(gen2-migration) `refactor` command should be idempotent

[iliapolo]

Is this feature request related to a new or existing Amplify category?

No response

Is this related to another service?

No response

Describe the feature you'd like to request

The refactor command should be retryable from any previous state:

• Running refactor a second time after a successful first execution should result in a no-op.
• Running refactor a second time after a specific category failure should pick up where it left off.

Describe the solution you'd like

We need to ensure our code runs in a "discover & execute" mode, instead of making any assumptions on the state of the source and target stacks.

Describe alternatives you've considered

None

Additional context

Same goes for --rollback.

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• ⚠️ This feature might incur a breaking change

[iliapolo]

Addressed as part of #14698

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.