[WIP] Module Code Ephemeral Migrator

[drewmullen]

Modules that contain secret-ful resources (those that generate and store secrets in state) that have been deployed prior to ephemerals release are a pain to migrate. In order for organizations to benefit from ephemerals they must provide a route for new deployments of their module without breaking old deployments.

A more thorough description of the problem can be found (here)

This skill should be run by module developers to analyze and appropriately upgrade their module code. Once complete they can publish a new major version of their module. As part of the skill execution it generates a customized, tailored migration guide / skill for the module's consumers. Make consumers aware of the new major version, provide them the generated SKILL and they can easily and safely upgrade their root to use the latest version.

Opinion: this skill directs the agent to create a new branch for the module changes and creates a PR. This allows for a summary of the changes, reasons why, etc.

[drewmullen]

Feedback from customers:

• Move the variable write functionality to the 1st step in the process. Most of the teams managing variables are platform teams
• Can consider using a provider set to implement the new variable
• Last mile user experience should be as simple as a version bump (ideally)