[test] Use @retroactive in test conformances

[lorentey]

The swift-collections test suite includes some test protocols to validate that dictionary- and set-like types provide the API surfaces that’s expected of their kind. These are being conformed to in the test targets, triggering new warnings on retroactive conformances.

Use @retroactive to silence such warnings.

Checklist

• I've read the Contribution Guidelines
• My contributions are licensed under the Swift license.
• I've followed the coding style of the rest of the project.
• I've added tests covering all new code paths my change adds to the project (if appropriate).
• I've added benchmarks covering new functionality (if appropriate).
• I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
• I've updated the documentation if necessary.

[lorentey]

(I expect this will fail on Swift 5.7, possibly 5.8.)

[lorentey]

@swift-ci test

[lorentey]

@swift-ci test

[lorentey]

Hm; dropping this from the 1.1.1 milestone, as we do not have a shipping Swift compiler that understands @retroactive yet.

[lorentey]

Swift 6 is out now; if @retroactive made it into the release, then we can apply this fix now. Rescheduling to 1.1.4.

[dnadoba]

The compiler got smarter and now doesn't require @retroative for conformances across modules if the type is from the same package: swiftlang/swift#75079

[xwu]

Incidentally, fully qualifying the conformance (instead of @retroactive) will allow the same code to compile regardless of language or compiler version.