Rework the ground object generators to a template system

[RndName]

Discussed in https://github.com/dcs-liberation/dcs_liberation/discussions/1984

In the current code we use many coded generators to create different ground objects. These are SAMs, EWRs, Fleet(Ships, Carriers, LHA), Missiles, Coastal and Armor Groups. These have the huge problem that they are hard to be maintained and unit positioning is a complex and time consuming job which makes it nearly impossible to support future changes and more complex layouts of different ground groups like sam sites.

To support the implementation of more advanced things like the SAM Asset pack as mod or similiar this should be changed to a template based system where templates are created from the DCS Mission editor so that units can be placed and and oriented precisely. This information should be enriched with coded information about the template like optional units, specific properties for the template and so on.

The future system:

• Completly template based, which ca be edited from the mission editor
• Faction senstive, so that every template will be validated if the selected faction has access to the unit or not
• Should allow better definition in the faction file so that only the requested category / type of the template will be defined and the rest is handled by the template system in accordance with the faction, doctrine and whatever could be possible.
• The template itself should handle the generation of the required TGO. So we will have it only at one place in the code
• To be readable and sensitive to reviews the complete Template information should be serialized to a JSON file from the .miz
• Additional information which is not accessible by the miz is also stored in this JSON File (for example the category of the template, the AirDefenseRange of Sam Systems or similar)

Things to do:

• [x] Preparation: Rework Ground Object & Migrate Generators to templates
• [x] Technical Implementation: Implement yaml descriptions for groups of units like SAM systems and the needed UnitClasses #1989
• [x] Generalization: Finally decouple Template from unit type and just define which classes can use the template (this step can be done after it's merged into develop. It's time consuming to identify similarities and extract them to generalized templates)

[RndName]

Discussion and diaries about this one can be found here: https://github.com/dcs-liberation/dcs_liberation/discussions/1984