Introduction of flight_mechanics into the assessment repo

Description

As promised for UNICADO II, the functionality to assess aircraft designs based on their flight-mechanics should be included. The new tool assessess different criteria found in the CS25, which can be individually chosen in the flight_mechanics_cs25 config file. For a detailed doucmentation, see the following branch: https://git.rwth-aachen.de/unicado/unicado.gitlab.io/-/tree/feature/documentation_flight_mechanic_assessment?ref_type=heads (some small changes must still be added to it, but the basic concepts are documented there).

Tested it and build an installer from this branch and the corresponding branch in libraries: https://git.rwth-aachen.de/unicado/libraries/-/tree/feature/updated_pyavl_modules?ref_type=heads.

Screenshots/Logs

All of the current designs (SMR-01, SMR-LH2-01, and LR-01) fullfill the flight mechanic criteria as expected. The results have been tested and validated for the configurations:

See the following projects folder with all the plots of the flight mechanics assessment: Configurations_with_flight_mechanics_enabled.zip

Testing Instructions

1. Download this branch. Using the assessment_manager, the new node <enable_flight_mechanics/flight_mechanics_cs25> can now be set to true and a converged aircraft design tested.
2. Make sure, the libraries "pyavlunicadopackage" and "pyavlpackage" inside the libraries repository are installed (see open MR with updates: libraries!83)
3. Also, flight_mechanics needs two new, third party python libraries: casadi and Jinja2, Make sure they are installed as well. (I added them to the installer, see MR: unicado-package!40 (merged))
4. Expect a run to currently take ~ 4min. The results will be given in a html report with a subpage for the different criteria.

Developer Checklist

• Code has been tested locally and/or in pipeline.
• documentation updated.
• (if applicable) impact of new dependencies reviewed and included in project.
• Merge conflicts resolved with the target branch.