Protect production data from developers

### Describe the feature you'd like to request

I want to restrict access to the production branches.
The developers should not have access to production data but must have access to the CLI and Amplify Studio to perform their tasks.
To do this, the access to the Amplify Studio users must be restricted to specific environments.

### Describe your use case and how the feature would improve your experience.

Right now I have the developers working with Amplify to develop functions, data tables, etc.
When my application is released, the production data should not be disclosed to the developers for security and legal reasons.
But now when you allow a user to access Amplify Studio, it has access to all the environments and the data they contain.

### Describe alternatives you've considered

Stop using Amplify and migrate to another platform that allows me to restrict access to production data.

### Additional context

_No response_

The issue names Amplify Studio users, production branches, environments, the CLI, and Studio access, but it names no files or tests. Start by locating the existing environment and user-permission flows; done means developers retain CLI and Amplify Studio access while production data is inaccessible.

Written by the indexing model from the issue text.