Backend environment 'dev' disappears from console

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d2w3wvbp5i5j6a

### Region

us-east-1

### Amplify Console feature

Not applicable

### Describe the bug

- The backend environment 'dev' is missing from the Console.
- I have 4 other backend environments displaying without a problem.
- However, 'dev' environment can be pulled by running `amplify env pull` with output 'Successfully pulled backend environment dev from the cloud.'
- Runing `amplify env pull` and `amplify push` can also confirm resources are running in the cloud as usual.
- As a result, frontend environment can not be set up with the backend for continuous deployment

### Expected behavior

'dev' environment should be visible and listed with other backend environments in the Console under the "Backend environments" tab.

### Reproduction steps

1. Set up 'dev' frontend and 'dev' backend environments with continuous deployment. Things are working as normal at this point.
1. Remove the 'dev' environment by running `amplify env remove dev`. The 'dev' environment is removed from the 'Backend environments' tab.
2. Note that frontend 'dev' environment still shows "Continuous deploys set up with dev backend (Edit)"
3. Run 'amplify env add'. and reuse the name 'dev' for the backend
4. Run 'amplify push'. Resources are provisioned in the cloud. `team-provider-info.json` is updated for the 'dev'
5. Code is committed to Github which triggers continuous deployment. The app is running without problem.
6. However, 'dev' backend is not showing under the 'Backend environments' tab.

### Build Settings

_No response_

### Additional information

_No response_

Reproduce the sequence using `amplify env remove dev`, `amplify env add`, and `amplify push`, then compare the Console's Backend environments tab with `team-provider-info.json`. Start at the backend-environment listing and continuous-deployment setup entry points; done means the recreated `dev` environment appears in the Console and remains usable for deployment.

Written by the indexing model from the issue text.