Resource Management to support managers created externally

[Mark-J-Lawrence]

Story

As an end-user, I want the ecosystem resource management service to run RM implemented by my internally written Galasa managers, so that I can have a maintained DSS without requiring to deliver my internal managers to the OS galasa repo.

Background

Users are encouraged to develop their own managers, and many of these will be bespoke and specific and will never be contributed back to OS Galasa.
These managers may create resources, which may need to be tracked via the DSS. To handle when there are problems with test runs, resulting in resources being left behind and orphaned from a test run, Resource Management should resolve the orphaned records and free/release the resource allocations.

Resource Management is a long running service in an ecosystem, usually started when the ecosystem installs. It is started from the Galasa boot image. This boot image contains all compiled jars of OS Galasa managers, resource management appears to simply use these locally available jars to find resource management providers.
From the logs, it does not appear to look anywhere else.

Therefore:

1. It is only currently possible to run resource management providers that exist within the Galasa OS repo. It is not possible to have the ecosystem run resource management provided by customer managers.
2. It is a long running service that isn't intended to be interrupted. So if it did support external managers, and someone made a change to one of their resource management providers. How do they indicate to resource management that it needs to restart itself to pick up the new version? (always pull image policy & delete pod maybe?)

@techcobweb has had a first idea of it cycling through a list of specific test streams loading a list of managers and using those.

I'm thinking the test stream might only have a few managers in there, so they would have to be combined with the managers in the boot image. Customers might also keep their managers & test seperate? In CICS, we also have the scenario of copying Galasa OS managers internally (keeping the same name), and we've modified their resource management, so would want to use those versions.
I don't know if being able to optionally point it to an OBR and a custom maven repo works?