Wardrobe - New Addon - System to modify wearables

[OverlordZorn]

WIP

When merged this pull request will:

• New Addon: Wardrobe
  Introduces a new system to modify currently worn gear.

For Example:

• Roll up/down your sleeves.
• Raise or lower the visor of helmets.
• Modify turbans from to the other variants.
• Combat Goggles <-> Balaclava with Combat Goggles <-> Balaclava

UX:

• ACE Self Interaction -> Equipment -> Wardrobe (if modifiable Item)
• Inventory -> CBA Context Menu on Wearable Slot

Compats for: GM, SOG, WS, RF

To Do:

- Rework the sound part to work with the sound_timing property.
- Rework the System to work with the components[] property.
-- Defines the components of an Items. For example: Dustglasses.
If it changes from an item with components to an item without the same components, it will deposit these components into the players inventory or vis versa, when changing to an item that requiers an component which the currently worn doesnt have, it needs to be in the inventory and will be removed when changed into.
-- Check for components is done, just need to return/remove components from/to the inventory.
- Fix the formating of the configs so the checks dont fail?
- Add more compats for the cdlc/vanilla stuff utilizing the component feature. (example: blk balaclava -> blk balaclava with eye protectors)
- Find better default sounds

• remove test mission from PR
  - Do the Documentation thingy

Bugs:

- RF Altin Helmets: Seems like the helmet without any visor can be modified into a visor-version.
Looks like it inherits wardrobe data?

IMPORTANT

⌚ If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.

❓ Development Guidelines are read, understood and applied.

✔️ Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

[Mike-MF]

• Newlines at end of files

[LinkIsGrim]

Big undertaking, and a bit of a nitpick, but I feel like this'd be more maintainable if wardrobe entries were kept in a CfgWardrobe root entry:

class ADDON {
    class Uniforms {
        class uniform_classname {
            ...
        };
    };
    class Glasses {
         ...
    };
};

Don't have to worry about inheritance, and easier for other components to hook into. Child classes could be a problem, though, but I don't think we'd want child classes to inherit their parent's variants anyway.