test: Run the FDv2 contract tests

[beekld]

Summary

Runs the cross-SDK FDv2 contract test suite against the SDK to exercise the data system end to end. The contract test service now accepts the harness's data system configuration and drives it through the public DataSystemBuilder. CI runs both the FDv1 and FDv2 suites.

The service advertises the fdv1-fallback capability so the fallback-directive scenarios run. There is no FDv2 capability flag, so the suite is selected by the harness version.

A suppression file skips scenarios that do not apply to this SDK:

• The payload-filter URL scenarios, since the SDK exposes no payload filter.
• The terminal FDv1-fallback scenario, since the SDK follows the directive's TTL rather than treating it as terminal.

---

Note

Overview
Adds cross-SDK FDv2 contract test coverage by extending the contract-test service and running both harness versions in CI.

The harness can now pass dataSystem configuration (initializers, synchronizers, FDv1 fallback). The service maps that to DataSystemBuilder with FDv2 streaming/polling builders and advertises the fdv1-fallback capability. Client setup builds a fresh transport per SDK component (shared connector only), matching normal SDK behavior.

CI/Makefile: bumps the contract-tests action to v1.3.0, runs FDv1 then FDv2 (version: v3) against one background service (stop_service: false on the first run), and adds local contract-tests-fdv2 / run-contract-tests-fdv2 with a dedicated suppressions file for the v3 harness (includes existing FDv1 skips).

Dependency: launchdarkly-server-sdk-evaluation 2.2.0 → 2.2.1 (patch).

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

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c7e15f6. Configure here.}

[keelerm84]

I don't think you should have to do all of this. If there isn't a fallback provided by the test harness, you should assume we don't want one set and just leave it as optional.

[beekld]

Done.

[keelerm84]

Do you still need this suppression once we changed the FDv1 configuration stuff?

[beekld]

Oh, good catch! I had thought that was failing because of the changes to our FDv1 fallback logic, but you're right. It was the bug with how we configured for contract tests.