CLI: Account for legacy framework values in automigration

[yannbf]

What I did

The automigrations were not account for a legacy framework value such as:

export default {
  framework: 'react'
}

So this PR fixes that (and fixes a small regression regarding community frameworks)

How to test

1. Run a sandbox for template, e.g. yarn task --task sandbox --start-from auto --template react-vite/default-ts
2. Change the framework field to react
3. Run automigrations

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[shilman]

Nice catch! 💯