Dphan/apigear next

[dorotaphanSiili]

1. Reorganize the repository:

• clean up structure
• partially solve [FEAT]: fix relative import #16 by splitting olink top level files into apigear olink module and examples with context path
• make a python module of each apigear module - group submodules _api _olink _impl into one folder for each apigear module and loose prefic module_name from directories. The usage then would be module_name.api instead module_name_api
• solve rest of [FEAT]: fix relative import #16 all generated files can be an import package (add toplevel _ _ init _ _.py and adjust all absolut imports to start with toplevel) and optionally also the distribution package (installable, with pyroject.toml) - ? can something more be done about it? requires discussion. For now a project that uses it adds a path

2. Implement features for apigear next

• import Implement imports feature for apigear next #22

• externals Implement support for extern types for apigear next #23

• UPDATE the cli version, when released (after Dphan/next qt and python alignment cli#146 )

Closes # #22 #23
Also closes
#27

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[w4bremer]

there should be a new line at the end of the file not on the first line?

[w4bremer]

That empty new line should also not be here.