Manage and Sync Amplify backend in multiple AWS accounts

### Amplify CLI Version

13.0.1

### Question

Hi people, now I'm struggling with manage Amplify in multi AWS accounts.
Now I have 2 AWS account: dev & staging with the same Amplify BE. I initialized from 2 different local machines.
Currently, I added resources on Dev Backend (like amplify add function,...), edit code, and push to git. In my staging env, I pulled the updated source code, and did `amplify push`. Unfortunately, It did not work.
As my understanding, Amplify manages backend resource based on `amplify/team-provider-info.json`, and it does not work well with git.
Anyone has experience of managing Amplify in multi AWS account, please help me.

Review how the Amplify CLI 13.0.1 uses amplify/team-provider-info.json when running amplify add function and amplify push across separate AWS accounts. Compare the Dev and staging workflows described in the issue and determine the expected multi-account synchronization behavior before identifying a testable change.

Written by the indexing model from the issue text.