flightDynamics: refactoring and summary of related issues

[MarAlder]

A revision of the flightDynamics analysis branch should bring more consistency to the CPACS data structure. The proposal is as follows:

flightDynamics analysis

The cpacs/vehicles/aircraft/model/analysis/flightDynamics groups trim, flyingQualities and flightPerformance analyses data

performanceRequirements

The analysis elements shown above can refer to requirements (via uID) for a particular aircraft (or helicopter) defined under cpacs/vehicles/aircraft/model/performanceRequirements. These elements are linking all the related data such as performanceMaps, configurations, weightAndBalance, missions and performanceCases. Related issues are #697, #698, #705 and #706. To avoid naming conflicts with the above analysis cases we decided to switch from the case nomenclature to the requirements nomenclature. However, to avoid very long element names subnodes are named with the short form ..Reqs/..req/.

flightPoints / performanceCases

The requirements shown above may again link to aircraft (and helicopter) independent flightPoints and performanceCases. Therefore, these elements are grouped under the vehicles node (see development guideline §3: Hierarchical classification of data in #704). The flightPoints are discussed in more detail in #694 and provide predefined sets of altitude, velocity and atmospheric data. They are currently only used for trim analysis and we will see how this approach proves in practice. Maybe they can be applied for other disciplines as well.

[MarAlder]

No counterarguments during the review period.