fix(lib): respect hclOutput app config

[jyecusch]

Related issue

Fixes #3875

Description

Only store and read the hclOutput configuration from the manifest (App class), respecting the value provided in the AppConfig, as well as the SYNTH_HCL_OUTPUT environment variable.

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

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[jyecusch]

I'm happy to make any changes requested or demo the issue. It may need to be two separate issues, since it would also be nice if the CLI didn't always set the SYNTH_HCL_OUTPUT env var, but running the application directly to get around that is reasonable.

I tried to get the tests running and passing locally following the steps in CONTRIBUTING.md, but I couldn't get them to pass successfully before making changes, so I'm unsure if any tests are broken as a result of this change. I'm happy to fix those too if there are.

[bogaertg]

We need this feature to synthesize HCL module.
Great job!

[tjholm]

@mutahhir @ansgarm Any issues with this one? This would be really useful functionality to get working.

[vercel]

@jyecusch is attempting to deploy a commit to the HashiCorp Team on Vercel.

A member of the Team first needs to authorize it.