[REFACTOR] Streamline codebase

[j-riebe]

Currenty, it's pretty hard to guess how the internal structure works.
This is mainly due to the "superfunction" that generates each plugin code and the missing abstractions inside (which lead to a lot of duplication).

• ClassRegistry Reduced code duplication in ClassRegistry and introduced sorting in the ObjectsPlugin #29
• EnumsPlugin
• FragementsPlugin
• FuncsPlugin
• InputsPlugin
• ObjectsPlugin
• OperationsPlugin

[j-riebe]

I would offer to submit one/some PR(s) to tackle this problem.

The first is #29 (ClassRegistry).

I'm currently working on adding abstractions to the Plugin Logic.
@jhnnsrs you can keep track of it here.

[jhnnsrs]

Great stuff! Theres really a need for a set of fresh eyes on this.

Some ideas:

From my perspective the schema driven generators (enums, inputs, objects) share a lot of common functionality and are pretty straightforward.

Fragments and Operations on the other hand are a bit messy as they generate classes on the fly during the recursion and handle some minor optimization (like not creating unnecessary zero-attribute classes).

Thanks a lot! I will be out for this weekend but happy to check it out start of next week.