Merging new api and lambda layer between branches does not show resources in amplify status.

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

v14.17.6

### Amplify CLI Version

7.6.20

### What operating system are you using?

Mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

### Amplify Categories

function, api

### Amplify Commands

add, env

### Describe the bug

Another developer created a feature in another git branch, and amplify env. He added an API gateway with a lambda function, and a new lambda layer, and deployed it to a shared environment. I merged his code changes from git into my environment, and ran amplify status, but his resources were not listed when running `amplify status`.

However, when I ran `amplify env checkout <>` followed by `amplify env checkout <>`, everything updated correctly. I could see his resources in the 'create' state when running `amplify status`.

### Expected behavior

Upon merging the code, I expected to be able to see the new resources in the 'create' state when running `amplify status`.

### Reproduction steps

1. Create a new lambda layer, and rest api in a shared branch and amplify env and deploy them and check them in.
2. In another branch, git merge the updates.
3. Run amplify status

### GraphQL schema(s)

--

### Log output

--

### Additional information

--

Reproduce the workflow by merging the shared branch, then running `amplify status` before and after the documented `amplify env checkout` commands. Trace the CLI handling for environment state, API Gateway, Lambda, and Lambda layer resources; done means merged resources appear in `amplify status` as `create` without switching environments.

Written by the indexing model from the issue text.