ci: use the floating contract-tests-v1 tag for the contract tests action

[kinyoklion]

Summary

Point every launchdarkly/gh-actions/actions/contract-tests usage at the floating contract-tests-v1 tag instead of a SHA pin, and drop the now-redundant release-link comments.

• Dependabot can't resolve versions for this monorepo action and proposed a downgrade (chore(deps): update launchdarkly/gh-actions/actions/contract-tests requirement to 2715574e04448246bc529a23a81766491bbc4aae #599: 5adb11f/v1.3.0 → 2715574/v1.1.0, which silently drops the enable_persistence_tests input). Closed that PR; the floating tag stops the bad suggestions.
• client.yml, server.yml, sse.yml were still on v1.1.0 and effectively move to v1.3.0.
• sse.yml sets enable_persistence_tests: false — the sse-contract-tests harness has no -enable-persistence-tests flag and exits 2 when passed it (v1.3.0 defaults the input to true).

Implementation details

contract-tests-v1 is force-updated to each new release by gh-actions' release-please workflow, so it currently points at 5adb11f (contract-tests-v1.3.0).

v1.3.0 vs v1.1.0 for the workflows that were behind:

• adds enable_persistence_tests (default true) → harness gets -enable-persistence-tests. Handled for SSE as above; for the server jobs the test service only advertises persistent-data-store-{redis,dynamodb} when built with use_redis/use_dynamodb, which those jobs don't do, so no additional suites run there.
• adds stop_service (default true), matching v1.1.0's hardcoded -stop-service-at-end.

Tradeoff: a floating tag is mutable, so this gives up SHA pinning for this first-party action.

Link to Devin session: https://app.devin.ai/sessions/01bce0d0f3894fccba4fe3fc117ff8b1
Open in Devin Desktop: https://app.devin.ai/desktop/session/01bce0d0f3894fccba4fe3fc117ff8b1?variant=devin
Requested by: @kinyoklion

---

Note

Overview
Switches all contract-test CI jobs to the floating contract-tests-v1 ref on launchdarkly/gh-actions/actions/contract-tests instead of mixed SHA pins (v1.1.0 / v1.3.0), and removes the redundant release-link comments above those steps.

Workflows that were still on v1.1.0 (client, server, sse) effectively pick up v1.3.0 behavior via the tag. sse.yml explicitly sets enable_persistence_tests: false on both contract-test jobs so the harness is not passed -enable-persistence-tests (unsupported for SSE; v1.3.0 defaults that input to true). Redis/DynamoDB server jobs keep enable_persistence_tests: true; only the action ref changes there.

Tradeoff: the floating tag is mutable, so SHA pinning for this first-party action is dropped in favor of simpler Dependabot/version alignment.

^{Reviewed by Cursor Bugbot for commit b674b86. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[kinyoklion]

We don't need to pin the internal actions, and dependabot was updating the pin incorrectly. So it will now float on v1.

[beekld]

Kinda confusing that it's "v1" of the GH Action, even when it's "v3" of the actual contract tests. But this is clearly an improvement anyway.