Implemented reporter class to handle both GUI and Headless install

Description

For testing purposes and in environments where no GUI exists a headless mode for installation is necessary. This mode already exists. Until now. the install function existed almost doubled in the install script. When changing the GUI install - the headless part needed to be updated as well.

The handling of GUI / headless is now implemented via a reporter class, which checks which mode is selected - and therefore decides how to process user input - and how to visualize installer output.

This mode is necessary for testing purposes:

• The performance test installs unicado from scratch and compares the workflow with and without module changes

Related Issue(s)

• aircraft-design#222

Screenshots

Testing Instructions

1. cmake --workflow --preset x64-windows-release
2. Execute UNICADOinstaller.exe (with GUI)
3. Execute in terminal UNICADOinstaller.exe --install-dir <InstallDirOfYourChoice> --backup (shall make a backup of your workflow with the current timestamp, if the install directory already exists)

Developer Checklist

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

Additional Notes

Add any information reviewers should focus on, e.g., specific files, functions, or changes of interest.