Lambda amplify/team-provider-info.json changes between env pushes

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

### How did you install the Amplify CLI?

curl

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

_No response_

### Amplify CLI Version

7.5.1

### What operating system are you using?

Mac

### Amplify Categories

function

### Amplify Commands

pull

### Describe the bug

I am opening this issue as a duplicate of https://github.com/aws-amplify/amplify-cli/issues/1194. I don't have the ability to post in that issue, so opening up a duplicate.
Unfortunately this problem it still happens in version 7.5.1

Everytime I switch environments and push code via github, and then do an `amplify pull`, the `s3Key` changes in `amplify/team-provider-info.json`.

### Expected behavior

s3Key should probably be environment dependent.

### Reproduction steps

1. working in `dev` git branch which is connected to `dev` environment
2. commit and push code using github
3. wait for it to be deployed
4. `$ git checkout main`
5. `$ amplify env checkout main`
6. `$ git merge dev`
7. `$ git push`
8. wait for the main environment to be deployed
9. `$ amplify pull`
10. You will see that `s3Key` has changed in `amplify/team-provider-info.json`

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

Reproduce the environment switch and deployment sequence using `amplify env checkout`, `amplify push`, and `amplify pull`, then compare `amplify/team-provider-info.json` before and after the pull. Trace where `s3Key` is written during the pull and determine what stable, environment-specific result should be verified when the reproduction steps complete.

Written by the indexing model from the issue text.