PMM-15347: Feature build for host-management bootstrap

[plebioda]

Pins the main dependency at PMM-15347-bootstrap-abort-per-member, the tip of the
stacked PR chain that drives MongoDB bootstrap from pmm-managed (#5949), adds the
bootstrap UI to Hosts/Operations (#5950), and adds abort + per-member settings
(#5951).

No url override: the branch is on percona/pmm, which is what .gitmodules already
gives this dependency.

Paired at run time with the SEP side-car image built from percona/SEP's
PMM-15347-om-integration (carries the matching om_bootstrap app, now activated in
sidecar/settings.yaml).

https://jira.percona.com/browse/PMM-15347

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4571-9b5d1f7
Client docker: perconalab/pmm-client-fb:PR-4571-9b5d1f7
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-9b5d1f7.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4571-9b5d1f7&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-9b5d1f7.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7402/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4571-7d9f12a
Client docker: perconalab/pmm-client-fb:PR-4571-7d9f12a
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-7d9f12a.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4571-7d9f12a&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-7d9f12a.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7413/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4571-a08488b
Client docker: perconalab/pmm-client-fb:PR-4571-a08488b
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-a08488b.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4571-a08488b&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4571-a08488b.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7414/

[travagliad]

FB run 35242727872 went red on a single leg — the Playwright e2e tests: @fb-instances job — and the failure was in setup, not a test: qa-integration/pmm_qa/external_setup.yml's Wait for redis exporter metrics endpoint task timed out (rc=124), so the test step was skipped and nothing was ever executed. It did not reproduce: a throwaway VM ran the same --database ps --database external --database haproxy setup against this PR's own image (perconalab/pmm-server-fb:PR-4571-a08488b) at pmm-qa main, all three setups passed, and 15 isolated repeats of that exact start-and-wait step across load levels up to load average 9 all came up in 0.17–0.71 s against the 60 s budget — so this is a lost/never-started exporter process, not a marginal timeout.

I re-ran the failed job on this run and it came back green, and the run as a whole is now green (attempt 2, 54 success / 3 skipped, 0 red) — so your change isn't implicated and your PR is clear. PMM-QA is tracking the stability of that setup step; the exporter is launched through a detached docker exec … nohup … &, which is the likeliest place for the process to be lost. Separately, and unrelated to this failure, the repro showed the setup's REDIS_EXPORTER_VERSION is silently a no-op — mv redis_exporter-* redis_exporter nests the requested build inside the pre-existing directory, so the exporter that actually runs is the hardcoded v1.14.0 rather than the requested v1.58.0; we'll fix that on our side.

---

Generated by Claude Code