[Feature]: Process manager as a service

Description

To assist with the UI deployment and continue identifying and establishing the deployment structure for the PM service, we should put the process manager into a pod and continue the development.

Potential impact radius

Small/Isolated

Reason for change

Updating the architecture towards the target long term plan. This also supports the effort to get the UI as standard.

Suggested implementations

Follow the practice of the other custom build usvcs defined in the microservices repository

We will need to consider how we distribute the address of the service. Initial thought is to suffix the implementation with a -usvc, or something similar that will allow a configurable process manager address.

Testing suggestions

Once deployed, the service should work as if it was a locally spawned instance. Note - until https://github.com/DUNE-DAQ/drunc/issues/829 is complete, only a single user will be able to use the process manager at a time.

Anything else?

This issue is used as the overarching parent issue for a big deliverable of this release, which is multi user support of the process manager