Save initial Amplify CLI version when creating new project

### 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

Migrating older projects to the latest Amplify CLI version is not easy right now. One of the problems is that users currently have to write down the Amplify CLI version with which the project was created with manually. This information is required to be able to migrate configurations etc. to the latest CLI version's standards, working with the Changelog file for example.

It would therefore be great if the CLI version a project is created with would be automatically be stored somewhere in the project.

### Describe the solution you'd like

When creating a new project with Amplify CLI, the current CLI version is written into a configuration file of Amplify. It can be overwritten manually once the project was manually migrated to match the standards of a newer Amplify CLI version.

### Describe alternatives you've considered

Manually write down the Amplicy CLI version every project was created with.

### Additional context

_No response_

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

- [ ] 👋 I may be able to implement this feature request
- [ ] ⚠️ This feature might incur a breaking change

Start by tracing the Amplify CLI project-creation flow and locating the configuration file where project metadata is stored. Determine how the current CLI version can be recorded and manually overwritten, then add or update coverage for creating a project and verifying that version metadata is present.

Written by the indexing model from the issue text.