[Feature Request] Migration and/or Renaming of the environments

### Description

As a customer I would like to have a way to easily migrate and/or rename the environments.

**A Customer Use-Case**

The customer started off with a development environment and started use this environment with end user. They wanted to rename the current environment to a new one and create a new "development" environment.

After this use-case I talked to @josefaidt and the current situation is:

- renaming an environment is not possible
- creating a new enviroment and migrating data to it is extremely hard.

In the documentation we mention environments to be similar to the git flows but simple operations like renaming is not possible.

### Categories

- [ ] Analytics
- [ ] API (REST)
- [X] API (GraphQL)
- [X] Auth
- [ ] Authenticator
- [ ] DataStore
- [ ] Notifications (Push)
- [ ] Storage

### Steps to Reproduce

_No response_

### Screenshots

_No response_

### Platforms

- [X] iOS
- [X] Android
- [X] Web
- [X] macOS
- [X] Windows
- [X] Linux

### Flutter Version

3.13.1

### Amplify Flutter Version

1.3.3

### Deployment Method

Amplify CLI

### Schema

_No response_

No files, tests, or entry points are named. Start by tracing the Amplify CLI environment-management flow for GraphQL and Auth, then determine how renaming and migration should preserve the existing environment's data and configuration. Done means a customer can rename an environment or move its resources to a new environment through a documented, verified workflow.

Written by the indexing model from the issue text.