Data driven container compat

[ZZZank]

This PR will allow developers and experienced users to add simple container support without touching any Java code of Bogo.

• scan for data in ./config/bogosorter/bogo.compat.json in game instance folder and ./bogo.compat.json in eveny valid mod jar
• conditional support, e.g. add support for IronBackpack only when mod with modid ironbackpack is present.
• complex condition: currently providing logical operation like not, and, or for combining multiple conditions, and advanced mod condition like RegEx matching for mod version.
• multiple support presets: generic support, custom slot begin/end and row size, mark only, remove only, mapped
• more dynamic "mapped" container support: currently allows using advanced condition to filter slots to be added to slot group. We might need some more adaptable Slot->ISlot mapper, blocked by Arcane archive support #82 .
• button position setter
• documentation
• in-game command for setting up template file and performing syntax check
• data-driven reflection, forming a "access sequence", the sequence must start with the container instance, and ends as an integer, ready for use in container support. Each access in this sequemce should be either getting a field, or invoking an instance method with no arg requirement
• data-driven ternary operator for more flexibility

[brachy84]

Overengineered and will never be used by anyone. Perfect

[ZZZank]

The person who opened this PR one year ago didn't realize that developers can use Bogo API via Groovy and/or CrT, so feel free to close this ¯\_(ツ)_/¯

[brachy84]

nah, ill merge it at some point

[brachy84]

Not a fan of using records with jabel

[ZZZank]

Using record saves the trouble of manually implementing all-arg constructor, getter, equals and hashcode. So if we are not switching to JVMDowngrader or Lombok, records with Jabel is by far the best solution

[brachy84]

Why linked? This is a hash map zoo

[ZZZank]

To keep their order when generating schemas. Not quite useful here, but for filters I want basic filters to come before compound filters (and, or, not).

[brachy84]

What this do?

[ZZZank]

See: https://json-schema.org/understanding-json-schema/structuring#dollarref . Example below:

{
    "type": "object",
    "properties": {
        "name": { "type": "string" },
        "address": { "$ref": "#/definitions/address" } // this will be linked to the 'address' below
    },
    "definitions": {
        "address": { // here
            "type": "object",
            "properties": {
                "street": { "type": "string" },
                "city": { "type": "string" }
            }
        }
    }
}

This is equivalent to:

{
    "type": "object",
    "properties": {
        "name": { "type": "string" },
        "address": { // inlined
            "type": "object",
            "properties": {
                "street": { "type": "string" },
                "city": { "type": "string" }
            }
        }
    }
}

I use this for recursive referencing object and breaking large schema into smaller bits

[brachy84]

Why do we need a list when we have the array?

[ZZZank]

When we dont want to include enum ordinal, we want the len below to be 0:

        for (int i = 0, len = indexed.size(); i < len; i++) {
            enum_.add(i);
        }

we can do this by making the indexed an empty list. This will be harder if we use T[] indexed because we need something like new T[0]