Currently, the bundle cfe_internal_limit_robot_agents is responsible for remediating a pathalogical condition where multiple concurrent instances of the same component daemon (i.e. cf-execd) are running.
This is known to be problematic for environments that run cfengine on the host, and also run cfengine inside of containers. Additionally, this has caused failures in deployment tests from component pids changing unexpectedly (because a process run under valgrind was seen as a duplicate).
For environments or individual agent runs where it's not unexpected that there will be multiple processes matching a single daemon component it would be nice to have the ability to avoid the policy that limits robot agents.
Introduce a new class mpf_disable_cfe_internal_limit_robot_agents that guards the evaluation of the cfe_internal_limit_robot_agents bundle.