Make config keys configurable with components

[ColinTimBarndt]

This is an implementation of config key components as mentioned in #9. Feedback is appreciated.

Resolves #9.

To Do:

• Component cache with tombstones. This would allow for efficient marker components that serve as boolean flags.
• Extract component implementation into another class for reusability outside of config keys.

[l-2-j]

Very C# like with how everything has interfaces and abstractions, which IG is what Banane wants... At least IMO should stick to consistent interface/class definition file split (&order) tho, can't say I see much wrong with the implementation.... because I don't feel like I have enough free time to dedicate to trying to figure out how this'll be used from a modder's perspective...

[l-2-j]

Also to keep old traditions alive;

[Banane9]

because I don't feel like I have enough free time to dedicate to trying to figure out how this'll be used from a modder's perspective...

From the defining a config perspective:

DefiningConfigKey<int> testKey = new("Test", ...)
{
    new ConfigKeyRange(0, 255)
}

The constructor still has the standard things too, but now more behavior can be added super easily. E.g. Quantities or Shared for Resonite.