Merge pman into pfcon

[jbernal0019]

Reasons:

• pman is tightly-coupled to pfcon. They are typically deployed as a pair, providing the "pfcon" service.
• pman's API is only used by pfcon in their internal network and is not exposed to the external world (e.g. to CUBE). Basically pfcon acts as the interface to pman.
• pman and pfcon are not being scaled independently.
• Merging these two microservices into one will remove some deployment complexity (one container as opposed to two networked containers) and some network overhead in the remote compute environment.
• Expected to make it easier the implementation of Server Sent Events (SSE) to stream the plugins' logs to CUBE and the UI realtime.