Muon view algs to access RoI collections inside their views

I don't think it should create any actual differences, but the muon algorithms running inside views were often accessing the RoI collection outside of that view. I have now changed that.

Potentially could change results where there are multiple RoIs in the outside-view collection, but only one within the view?

Algorithms within a view accidentally accessing an out-of-view container is a potential source of error, although is fine if intended. I've been searching for accidental cases.

This merge request affects 1 package:

• Trigger/TriggerCommon/TriggerMenuMT

added Trigger TriggerMenu master review-pending-level-1 labels

Jenkins please retry a build

Job restarted after the finish of a scheduled intervention on the Jenkins CI server

This merge request affects 1 package:

• Trigger/TriggerCommon/TriggerMenuMT

CI Result SUCCESS (hash 708803d4)

	Athena	AthSimulation
externals
cmake
make
required tests
optional tests

Full details available on this CI monitor view
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 7060]

Approving MR. Eric, L1

added review-approved label and removed review-pending-level-1 label

merged

mentioned in commit 56035350

added sweep:ignore label