Build Modules from Various Sources

[skorfmann]

This adds a new package, @cdktf/hcl2json which is being used to to convert HCL to JSON. This is required to get the inputs and outputs for a given module.

This aims to fully resolve #522

[skorfmann]

In general, this is ready for review. I'm gonna adda a few test cases around modules, fix the existing tests and perhaps extract a few classes into dedicated files. Conceptually it's going to stay like this for now.

On a high level, this merged the module and provider schema generation. Both is now generated from a Terraform config, where the module schema is processed via @cdktf/hcl2json.

The naming part for modules is a bit tricky. Since this supports various module sources now, a simple string source doesn't cut it anymore. Hence, this introduces an additional option to define modules - both options will be valid:

{
  terraformModules: [
    "terraform-aws-modules/vpc/aws@2.39.0",
    {
      name: "AwsVpc",
      source: "terraform-aws-modules",
      version: "2.39.0"
    }
  ]
}

Furthermore, there's a breaking change regarding the generated module name. Given the following config:

{
  terraformModules: [
    "terraform-aws-modules/vpc/aws@2.39.0",
  ]
}

Before a class Vpc would have been generated. Now it will generate a class name TerraformAwsModulesVpcAws. This makes the name handling simpler. An upgrade path for a user with existing module config would be to change to a module configuration object like

{
  terraformModules: [
    {
      name: "Vpc",
      source: "terraform-aws-modules",
      version: "2.39.0"
    }
  ]
}

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