Code Mappings per Environment.

### Problem Statement

I have set up the Code Mapping for our project, with the code repository in GitHub.
This is fine for having either
- Issues from our staging environment mapped with our staging branch.
- Issues from our production environment mapped with our main branch.

But I cannot set both, and I cannot set two.
The state of the code in our Staging environment is changing regularly and issues logged from our production environment would then have the wrong mapping setup if we have the code mapping setup for our staging branch.

It would be useful to have multiple code mappings setup for a repository that differ in their Environment and Branch.

### Solution Brainstorm

Add another attribute to Code Mappings that offers differentiation between Environments.

### Product Area

Issues

Edit:
I should add, that the "Stack Trace Root" and "Source Code Root" fields are not sufficient to achieve this, as they are identical between Environments.