[FEATURE] Automate dependency upgrade with popular solutions (renovate, github dependabot) inside terramate code generation

[luong-komorebi]

Is your feature request related to a problem? Please describe.

• As a user, I want my dependencies to be automatically updated and comprehended by an automation system so that my infrastructure components are updated with latest versions (security, bug fixes, new features)
• As a user, I want to generate "required_providers" code by terramate so that versions are consistent through out stacks

Combining the two stories above, I believe it makes sense for us to support terramate as a language in big dependency automation system. Right now, the main blocker is when versions are put into terramate code generation, when these systems automatically update dependencies, they can only updated the generated code, not the main code, leading to automation mostly fails with terramate run because generated codes now diverged from source

Describe the solution you'd like The best solution would be contributing to the upstream of these automation system. For inspiration,

• Rennovate and terragrunt: docs, relevant codes
• Github dependabot: relevant codes

Describe alternatives you've considered Read a terraform string from a file then somehow passed it into "content" block, so that we can keep dependency a raw hcl block which can be read by the above system. This is not successful Leave versions outside of generated code, probably in lockfile or somewhere else. This defeats purpose of versions, especially required_versions

Additional context Add any other context or screenshots about the feature request here.