Streamline Usage of Prebuilt Providers

[skorfmann]

This streamlines the experience of using prebuilt Terraform providers:

In cdktf.json: When no terraformProviders and terraformModules are set, the check for the presence of codeMakerOutput is omitted. This allows running the check, even when using a prebuilt provider alongside custom generated providers or modules.

In addition, this pull request, introduces a minimal template (see #308). This is a good starter when using prebuilt providers.

Last but not least, it adds a bit of documentation.

Fixes #98
Fixes #284
Fixes #275
Fixes #308
Fixes #320

[jsteinich]

I'm looking forward to using pre-built providers

[jsteinich]

I"m curious how this list was chosen. I was expecting all hashicorp official providers.

[skorfmann]

Mostly popularity, Github because I want to build an example case for Level 2 constructs and Null because it's a building block which useful for things like ecr asset

The current state is an advanced proof of concept. Mid / long term I think there would be more providers if not all at some point. For now, the goal is collecting feedback and building some examples to see if the UX is going in the right direction.

Things like:

• versioning (version constraints for peer dependencies, how does it work in Python, ...)
• major version changes (e.g. AWS 2.0 -> 3.0)
• improve the auto publish pipeline
• building upon these providers
• adding tests to the provider publish pipeline

[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.