Utilizing Containerized TDS/TM in the tool-meister-start Script

[Maxusmusti]

Allow users to leverage the power and flexibility of the containerized tool-meister and tool-data-sink in traditional pbench-agent benchmarks. Will allow for:

• Multi-node benchmarks with the pbench-agent installed on only the controller
• Full tool support (pcp, node-exporter, dcgm, etc.) without any additional installs
• Avoid local install conflicts

Behavior:

• Run any benchmark (like user-benchmark, etc.) that utilizes the tool-meister-start script
• Launches TDS container on controller instead of traditional TDS process
• Launches TM containers on all registered nodes instead of traditional TM process
• Both connect to the same controller redis server that tool-meister-start regularly starts up, the rest operates identical to a traditional run (though now remote nodes only need podman, and all tools are "installed" and usable)
• NOTE: Perhaps make this an option enabled through an arg or env var?

[portante]

@Maxusmusti, can you add more details to the description regarding what the behavior should be when this feature is enabled? In other words, if someone was to pick up this issue 3+ months from now, would they have enough context to know where to begin implementing this request?