Add simple_subtype_field_names NameProposer

[supersaiyansubtlety]

Adds the option of naming simple types' subtypes based on a transformation of the super simple type's name.

Heavily based on the simple types proposer.

example use case: Entity subclasses with suffix Entity -> PiglinEntity fields and params are named piglin

---

Additional fixes

• SimpleTypeSingleIndex:
  • used lower case names for constant conflict detection
  • could give outer class fields an inner class as a parent (no known consequences)
  • inheritance ancestor order iteration was not consistent; inheritance overrides didn't always work
• ConflictFixProposer looked up mappings using deobf params, breaking it for deobf method param conflicts which can arise from DelegateParametersNameProposer
• simple type verification test flakiness; separates it into its own test input source set and catches thrown exception instead of capturing log output

---

Format

Uses the same registry as simple types and expands "inherit" to allow object values. Inherit can now take any of the following forms (also see schema):

"inherit": true removed

"inherit": {
  // equivalent to old "inherit": true
  "type": "DIRECT"
}

"inherit": {
  // names subclass fields by checking if their type ends with the suffix, then names them after their type with the suffix removed
  "type": "TRUNCATED_SUBTYPE_NAME",
  "suffix": "Entity"
}

"inherit": {
  // names subclass fields by checking if their type matches the pattern, then names them after their type with the replacement applied
  "type": "TRANSFORMED_SUBTYPE_NAME",
  "pattern": "(.+)BlockEntityRenderer",
  "replacement": "$1Renderer"
}

---

Todo:

• don't do subtype naming for abstract classes (so LivingEntitys aren't named living)
• more tests

[OroArmor]

I think this would be better as an extension to the simple type field name that already exists, with maybe "inherit_suffix": "Entity" or something.

[supersaiyansubtlety]

I think this would be better as an extension to the simple type field name that already exists, with maybe "inherit_suffix": "Entity" or something.

I'm not sure how that would work.
This proposer is dynamic because it's based on already mapped class names. I don't see how that could be combined with existing simple type names.

[supersaiyansubtlety]

I guess they could be combined and just be doing effectively two separate things.
I don't see a technical reason to combine them though.

[supersaiyansubtlety]

Looking into an issue I found by trying the Entity subtype on MC mappings

[supersaiyansubtlety]

diffs for each of the examples in the OP; some spooky diffs are mixed in
entity-qmap.diff.txt
ber-qmap.diff.txt

[ix0rai]

I guess they could be combined and just be doing effectively two separate things. I don't see a technical reason to combine them though.

i agree, i think it's a little cleaner to keep them separate

[supersaiyansubtlety]

I've made substantial changes, so new diffs:
entity-qmap.diff.txt
ber-qmap.diff.txt

[ix0rai]

looks great, this feature is really well done! just wondering why you reimplemented toLowerCase() lol

[supersaiyansubtlety]

this implementation does not go in breadth-first order
QuiltMC/enigma#347 will fix this
converting to draft until 347 can be included