Only shows jobs relevant to environment under operations

Problem to solve

Currently when navigating to Operations -> Environments, I see production jobs under the run tab for staging and should not.

see https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8374#note_246898917, and relevant part of that below:

I found that if I triggered a rollout 100% from staging under Operations -> Environments, that it actually runs the rollout 100% on production instead of staging...see below, this is very confusing UX behavior (I think I understand why it runs on production, but not why it would show up as an option on staging)

Proposal

Staging should not show jobs that only affect production (i.e. not its own environment)

What does success look like, and how can we measure that?

Staging in the example above would not show the production rollout jobs

Links / references

/cc @tkuah