fix(pacmak): Generate Relative Module Imports in Python

[skorfmann]

The goal of this PR is, to find a way for generated Python code to work with namespaced modules regardless of the way it is consumed. While the current implementation of submodule imports seem to work fine when distributed as packages, it's breaking apart when the generated code is imported relatively as part of a single code base. That's what we do in cdktf and the reason why we have locked jsii to 1.37.0 at the moment.

The general idea is, to generate relative imports rather than fqn imports in Python. This could be a potential way to address #3078

# Before    
import jsii_calc.submodule
import jsii_calc.submodule.nested_submodule
import jsii_calc.submodule.nested_submodule.deeply_nested

# After
from . import submodule
from .submodule import nested_submodule
from .submodule.nested_submodule import deeply_nested

Besides from a few snapshots being changed, it seems like the tests are still working with this change. However, I'm not sure about the general implications. So, this entire PR is really meant to be a conversation starter.

I have confirmed that an import like import . from some_aws_namespace would work for us in cdktf.

References

• Python submodule import not found #3078
• fix(python): unknown type when submodule is not loaded #3049
• Python cdktf imports throwing error hashicorp/terraform-cdk#1152
• chore(deps): relax jsii dependencies hashicorp/terraform-cdk#1288

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[mergify]

The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged.
[Conventional Commits]: https://www.conventionalcommits.org

[RomainMuller]

LGTM - Thanks for fixing that!

[mergify]

Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it!

[mergify]

Merging (with squash)...