fix(e2e): globalSetup wrote to the SHARED instance on every run

[rubenvdlinde]

The bug

Both of globalSetup's occ helpers hardcoded the container:

docker exec -u www-data nextcloud php occ openbuild:seed-hello-world-fixture
docker exec -u www-data nextcloud php occ config:system:set ratelimit… \
  && docker exec nextcloud apache2ctl graceful

nextcloud is the shared dev box on :8080. The suite is driven with PLAYWRIGHT_BASE_URL pointing at the disposable container on :8099 — so every run seeded fixtures into, set a system config on, and gracefully restarted Apache in an instance the tests were not asserting against.

A cross-instance write on every single run, and silent. It only surfaced because :8080 went into maintenance and the seed began logging "hello-world fixture seed failed (specs needing it will fail)" while the run otherwise looked fine. Same class of drift as the base-URL bug that tests/e2e/support/baseUrl.ts documents — and the same failure mode as the incident that had a session's numbers retracted.

The fix

The container is resolved from the published port of the instance under test (docker ps --filter publish=<port>), not by name.

Name matching is precisely what makes this trap easy: docker ps -f name=nextcloud is a substring match and will happily return nextcloud, ob-vue3-e2e-nextcloud, or a stale nextcloud-old. The port is the one thing that cannot disagree with the URL the tests actually talk to.

When the container can't be resolved, both helpers skip with an actionable message (OPENBUILD_E2E_CONTAINER, or the existing per-command overrides) and deliberately do not fall back to a hardcoded name — the fallback is the bug. The rate-limit helper says so explicitly, since it writes config and restarts Apache and must never guess an instance.

globalSetup now also logs the resolved instance and container, so a mismatch shows up in the first line of any run instead of being inferred from a failure three specs later.

Verification

[globalSetup] instance under test: http://localhost:8099 (container: ob-vue3-e2e)
[globalSetup] hello-world fixture: hybrid example already present — nothing to do.

The seed now succeeds against the correct container (it had been failing while :8080 was in maintenance), and applicationCard stays 4/4 green. ESLint clean apart from the repo-wide pre-existing n/no-unpublished-import.