Review Possible Fixes for Import Issues

[SirGankalot]

User story

1. As a Developer
2. I want to test around with the currently problematic imports
3. So that the imports and test cases can run smoothly on python 3.10,11,12 (currently only 3.12)

Acceptance criteria

• Document all steps in the wiki
• Search for possible fixes based on our enviroment
• Current problem the imports need to be set to function across the python versions,
  the base tooling of mamba might be the problem, because it can not determine what package version works across python versions
• Check if there are other tools out there that can handle our enviroment
• Test if said tools or diffrent combinations work
• If you have other fixes or idears you are welcome to try them out
• If new informations or problems arise please communicate them with the devs working on Merge Project to Core Repository and Adjust based on Shell Feedback #122 as well as shell themselfs
• The other way around you might get new informations from shell via the devs on Merge Project to Core Repository and Adjust based on Shell Feedback #122 or via email
• Please still check regularly the merge request for possible questions from shell about import problems and answer/implement them if possible

Definition of done (DoD)

• Acceptance criteria are met.
• Work are pushed to the Github repository.
• Create a branch for each backlog items (coding)
• A pull request is created for each related branch.
• The work products in the pull requests are reviewed.
• The corresponding branches are merged and closed.
• The bill of materials section of the planning documents is updated.
• The software architecture should be updated based on features changes.
• Work needs to be documented in the corresponding wiki section
• For new features unit test have to be written.
• Update our forked repository with the latest RTDIP release.
• All unit tests must pass successfully in the CI pipeline.
• If the task involves coding, the implementation is integrated into the RTDIP framework and verified to function correctly within it.

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release