Rewrite test template for Queen-Attack practise exercise to wotk with Swift Testing

[Sencudra]

What is the problem?

During the mentoring session I've figured out that there is a problem with running tests in CI for Queen Attack exercise.

Looks like test are passing, but for some reason test results are not passed to external artifacts.

Build complete! (11.16s)
Test Suite 'All tests' started at 2025-06-18 19:55:45.422
Test Suite 'debug.xctest' started at 2025-06-18 19:55:45.423
Test Suite 'QueenAttackTests' started at 2025-06-18 19:55:45.423
Test Case 'QueenAttackTests.testCanAttackOnFirstDiagonal' started at 2025-06-18 19:55:45.423
...
...
19:55:45.525	 Executed 13 tests, with 0 failures (0 unexpected) in 0.102 (0.102) seconds
Test Suite 'debug.xctest' passed at 2025-06-18 19:55:45.525	Executed 13 tests, with 0 failures (0 unexpected) in 0.102 (0.102) seconds
Test Suite 'All tests' passed at 2025-06-18 19:55:45.526 Executed 13 tests, with 0 failures (0 unexpected) in 0.102 (0.102) seconds◇ 
Test run started.
Testing Library Version: 6.1.2 (d6b70f9ef9eb207)
Target Platform: x86_64-unknown-linux-gnu✔ 
Test run with 0 tests passed after 0.001 seconds.

The possible problem is discussed here. TLDR; Separate test drivers for XCTest and Swift Testing, cannot be summarized in the same report.

Proposed Solution

Rewrite to Swift Testing and forget about XCTest.

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[github-actions]

Hello 👋 Thanks for your PR.

This repo does not currently have dedicated maintainers. Our cross-track maintainers team will attempt to review and merge your PR, but it will likely take longer for your PR to be reviewed.

If you enjoy contributing to Exercism and have a track-record of doing so successfully, you might like to become an Exercism maintainer for this track.

Please feel free to ask any questions, or chat to us about anything to do with this PR or the reviewing process on the Exercism forum.

(cc @exercism/cross-track-maintainers)