Always display the control devices with the wing

[ole-alb]

Description

Closes #1225

Always display the control surfaces when the whole aircraft or just the wings are displayed in the tiglecreator.

How Has This Been Tested?

Screenshots, that help to understand the changes(if applicable):

Checklist:

Task	Finished	Reviewer Approved
At least one test for the new functionality was added.	yes does not apply	OK
New classes have been added to the Python interface.	yes does not apply	OK
The code is properly documented with doxygen docstrings	yes does not apply	OK
Changes are documented at the top of ChangeLog.md	yes does not apply	OK

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.97%. Comparing base (7166d1d) to head (3c9f87d).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1233   +/-   ##
=======================================
  Coverage   71.97%   71.97%           
=======================================
  Files         308      308           
  Lines       29541    29541           
=======================================
  Hits        21261    21261           
  Misses       8280     8280           

Flag	Coverage Δ
unittests	71.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ole-alb]

I also encountered a further design decision we should discuss. How do we want to handle transformed flaps? If we open the flap transform window, move the flaps around and then display the whole aircraft, the borders are still at the original position.
(This problem should be resolved with the implementation of a scene graph, but I still wanted to mention it).
What do you think @joergbrech @svengoldberg

[joergbrech]

This problem should be resolved with the implementation of a scene graph, but I still wanted to mention it

Yes, I agree. I suppose the changes in this PR are more a quick fix. Let's not overdo it and focus on the scene graph. Here, this issue should be resolved.