fix(hcl2cdk): handle JSII Rosetta translation properly

[DanielMSchmidt]

Related issue

Fixes #2646

Description

JSII Rosetta needs to have compilable code in order to determine the correct classes to use in Non-TS languages.
This PRs aims to do this for cases where we have node.js bindings in the same folder this runs in. This is the step on the way of making it work in all cases

Follow up work

I decided against doing a full test setup here that synthesises across all languages to cut scope from this PR, I'd suggest we do this in separate follow up PRs.

Checklist

• I have updated the PR title to match CDKTF's style guide
• I have run the linter on my code locally
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if applicable
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works if applicable
• New and existing unit tests pass locally with my changes

[team-tf-cdk]

This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[team-tf-cdk]

This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[DanielMSchmidt]

This should also have fixed #2647 but the snapshots beg to differ for some languages, I'll double check this with the test repository to see if the output is the same. For now we will consider #2647 a separate issue

[team-tf-cdk]

This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[mutahhir]

Nice change 👏🏽

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.