Add partial prototypes, for defining and modifying prototype data with the same ID in different files

[DrSmugleaf]

Doc bible attached

For downstreams of downstreams, you can specify the load order:

PartialDirectory(
    new ResPath("/Prototypes/_ForkOne"),
    new ResPath("/Prototypes/_ForkTwo")
);

Or

PartialDirectory(new ResPath("/Prototypes/_ForkOne"));
PartialDirectory(new ResPath("/Prototypes/_ForkTwo"));

Non partial directories are loaded before any partial ones.

Examples:

Add three loadouts and remove one:

- type: loadoutGroup
  id: MailTechnicianJumpsuit
  loadouts:
  - CargoTechnicianJumpsuitAlt
  - CargoTechnicianJumpsuitFormal
  - CargoTechnicianJumpskirtFormal
  - !Remove MailTechnicianJumpsuitSenior

Remove a component and remove a spawned from Butcherable:

- type: entity
  id: BaseMobHuman
  components:
  - type: !Remove LanguageKnowledge
  - type: Butcherable
    spawned: !Remove {}

To make it not add the prototype if the original one does not exist or is later removed:

- type: !PartialOnly entity
  id: BaseMobHuman

[kontakt]

Afterlight string

[kontakt]

Convention is no indent on xmldoc.

[deltanedas]

should have a distinct syntax (probably partialType instead of type) so its easy to rg, as well as always being an error if a non-partial one doesnt exist by default imo. otherwise the lazy way of doing it for 99% of usecases results in broken prototypes that might survive yml linter

[DrSmugleaf]

should have a distinct syntax (probably partialType instead of type) so its easy to rg, as well as always being an error if a non-partial one doesnt exist by default imo. otherwise the lazy way of doing it for 99% of usecases results in broken prototypes that might survive yml linter

One of the big things this is trying to fix is porting YML between downstreams being mighty annoying, if it always threw an error that would still be almost as annoying
I originally had it throw an error, I could make that configurable if that's wanted, but without it it makes it easier to lint away if you wanted to, if it threw an exception you would need to catch that in the linter, or a test