Decoupling and generalization of templates

Improvement for factions and templates which will allow decoupling of the templates from the actual units
- Implement UnitGroup class which matches unit_types and possible templates as the needed abstraction layer for decoupling.
- Refactor UnitType, Add ShipUnitType and all ships we currently use
- Remove serialized template.json and migrated to multiple yaml templates (one for each template) and multiple .miz
- Reorganized a lot of templates and started with generalization of many types (AAA, Flak, SHORAD, Navy)
- Fixed a lot of bugs from the previous reworks (group name generation, strike targets...)
- Reorganized the faction file completly. removed redundant lists, added presets for complex groups / families of units like sams
- Reworked the building template handling. Some templates are unused like "village"
- Reworked how groups from templates can be merged again for the dcs group creation (e.g. the skynet plugin requires them to be in the same group)
- Allow to define alternative tasks

gen/flights/flightplan.py

@@ -1305,7 +1305,7 @@ class FlightPlanBuilder:
             for group in location.groups:
                 if group.units:
                     targets.append(
-                        StrikeTarget(f"{group.name} at {location.name}", group)
+                        StrikeTarget(f"{group.group_name} at {location.name}", group)
                     )
         elif isinstance(location, Convoy):
             targets.append(StrikeTarget(location.name, location))
@@ -1318,7 +1318,7 @@ class FlightPlanBuilder:
 
     @staticmethod
     def anti_ship_targets_for_tgo(tgo: NavalGroundObject) -> List[StrikeTarget]:
-        return [StrikeTarget(f"{g.name} at {tgo.name}", g) for g in tgo.groups]
+        return [StrikeTarget(f"{g.group_name} at {tgo.name}", g) for g in tgo.groups]
 
     def generate_anti_ship(self, flight: Flight) -> StrikeFlightPlan:
         """Generates an anti-ship flight plan.