chore: update startup integration tests [AS-1463]

[kaixi-wang]

Rationale

• https://github.com/voxel51/voxel-hub/pull/2233 added CAS and API startup messages that we can start relying on instead

Review Priority

• high
• medium
• low

Changes

Checklist

• This PR maintains parity between Docker Compose and Helm

Testing

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e56ed428-53a5-4dc9-b993-0b7af152eff0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

Five integration test files update expected container and pod log message assertions across Docker Compose and Helm deployment scenarios. Expected log patterns for teams-api and teams-cas services change from previous readiness/worker indicators to explicit startup messages.

Changes

Service startup log assertions

Layer / File(s)	Summary
Docker Compose log assertions tests/integration/compose/docker-compose-internal-auth_test.go, tests/integration/compose/docker-compose-legacy-auth_test.go	Docker Compose internal-auth and legacy-auth test cases across all compose modes (compose, composePlugins, composeDedicatedPlugins, composeDelegatedOperations) update expected log substrings from motd.py and ✓ Ready in to FiftyOne Teams API starting up and FiftyOne CAS starting up.
Helm pod log assertions tests/integration/helm/helm-internal-auth_test.go, tests/integration/helm/helm-legacy-auth_test.go, tests/integration/helm/helm-topology-spread-constraint_test.go	Helm internal-auth, legacy-auth, and topology-spread-constraint test cases across plugin scenarios (builtinPlugins, sharedPlugins, dedicatedPlugins) update expected pod log values from readiness/worker-start patterns to FiftyOne CAS starting up and FiftyOne Teams API starting up.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• mo-getter

Poem

🐰 The tests now wake up fresh and bright,
With startup messages, shiny and right,
From compose to helm, they all agree—
FiftyOne's launching for all to see! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description follows the template structure with Rationale, Review Priority (low selected), Changes checklist (Docker Compose/Helm parity confirmed), and Testing sections included.
Title check	✅ Passed	The title accurately reflects the main change: updating startup-related integration tests.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kacey/fix-flaky-api-log-tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[kevin-dimichel]

@kaixi-wang - while we are at it, can we update https://github.com/voxel51/fiftyone-teams/pull/2539 to be something more meaningful than { name: "John Doe" }? When we do, we can update the checks here too.

[kaixi-wang]

https://github.com/voxel51/fiftyone-teams/pull/2788 for the teams-app

[kaixi-wang]

not sure why the integration tests are failing. Ran MONGODB_BIND_PORT=27019 go test -count=1 -timeout=15m -v -tags integrationComposeLegacyAuth -run 'TestDockerComposeUpLegacyAuth' and they are passing:

[kevin-dimichel]

Thank you for running it locally.

Let's carry on. We'll see the issues on the release branch to main branch PR too. : /