fix(ee-multicloud-public): port OCP container group entrypoint fixes

[rut31337]

Summary

Port entrypoint fixes from rhpds/agnosticd-v2 that enable ee-multicloud-public to work on AAP 2.4+ when running jobs via container groups on OpenShift.

This ports the following PRs:

• rhpds/agnosticd-v2#133 — Kubernetes detection + ansible-playbook wrapper
• rhpds/agnosticd-v2#162 — file existence guards for v1 projects
• rhpds/agnosticd-v2#164 — variable scoping fix for set -eu

Problem

When AAP runs jobs via container groups on OCP, pods start with ansible-runner worker --private-data-dir=/runner. Job data (inventory, extravars) arrives via the receptor stdin stream after the entrypoint completes — it is not on disk at entrypoint time.

The current entrypoint does a simple exec "${@}", which works for basic cases but:

1. Does not set ANSIBLE_COLLECTIONS_PATH, so AAP may not find installed collections
2. Does not handle dynamic dependency installation for projects that use it
3. Has no awareness of the three different execution contexts (OCP container group, AAP bare-metal execution node, ansible-navigator)

Solution

entrypoint.sh

• Kubernetes detection via KUBERNETES_SERVICE_HOST env var (injected by k8s into every pod)
• ansible-playbook wrapper installed at /runner/.ep-wrapper/bin/ that shadows the real binary — when ansible-runner later invokes ansible-playbook, the wrapper installs dynamic dependencies first (now that job data is available), then execs the real binary
• AAP execution node detection via -u root argument pattern for bare-metal AAP
• File existence guards on install_dynamic_dependencies.yml — v1 projects that lack this file skip gracefully
• ANSIBLE_COLLECTIONS_PATH set explicitly with /home/runner/.ansible/collections, /collections, and /usr/share/ansible/collections
• Collections directory created with correct permissions

ansible.cfg

• Added collections_path to match the entrypoint's ANSIBLE_COLLECTIONS_PATH

Compatibility

• agnosticd v1 projects: The install_dynamic_dependencies.yml file won't exist, so all three code paths (K8s, AAP, navigator) skip dependency installation gracefully via the [ -f ] guard
• agnosticd v2 projects: Full dynamic dependency installation works across all execution contexts
• ansible-navigator: Continues to work via the shift 2 fallback path
• Bare-metal AAP: Detected via -u root pattern, same as upstream

Test plan

• Run a v1 project job on OCP container group — should complete without entrypoint errors
• Run a v1 project job on bare-metal AAP execution node — should skip dependency install gracefully
• Run with ansible-navigator locally — should work as before
• Verify ANSIBLE_COLLECTIONS_PATH is set correctly in all three modes