Stop loading uber OBR bundles containing resource cleanup classes when a test stream is given

[eamansour]

Why?

For galasa-dev/projectmanagement#2511

At the moment, when a user provides a test stream to configure the custom resource monitor, the framework adds the test stream's OBRs to the list of OBRs to look through to find classes implementing the IResourceManagementProvider interface.

The custom resource monitor shouldn't be loading bundles in the uber OBR - those bundles are already loaded in the Galasa service's normal resource monitor pod.

Changes

• When a test stream is passed to resource management, the framework will now only look through OBRs that are configured into the test stream to find bundles containing IResourceManagementProvider classes
• Switch to using a list of bundles rather than a set in case bundles need to be loaded in a specific order given by the OBR