Introduce SpeziTesting library and migrate some tests to Swift Testing

[Supereg]

Introduce SpeziTesting library and migrate some tests to Swift Testing

♻️ Current situation & Problem

This PR starts the effort of replacing XCTest with Swift Testing. We replaced the XCTSpezi library with SpeziTesting. This can be adopted by anyone even if using with XCTest as just the naming semantics changed.
Secondly, this PR already migrates some of the unit tests to use Swift Testing. Some remain unchanged as we also require the underlying XCTRuntimeAssertions to be updated.

⚙️ Release Notes

• Introduce SpeziTesting library.
• Migrate some test to Spezi Testing.

📚 Documentation

--

✅ Testing

--

📝 Code of Conduct & Contributing Guidelines

By creating and submitting this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• I agree to follow the Code of Conduct and Contributing Guidelines.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 86.95%. Comparing base (5adc30e) to head (59033d3).

Files with missing lines	Patch %	Lines
Sources/XCTSpezi/Exports.swift	0.00%	6 Missing ⚠️
Sources/Spezi/Spezi/Spezi+Preview.swift	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
- Coverage   87.44%   86.95%   -0.48%     
==========================================
  Files          51       52       +1     
  Lines        1687     1693       +6     
==========================================
- Hits         1475     1472       -3     
- Misses        212      221       +9     

Files with missing lines	Coverage Δ
Sources/SpeziTesting/DependencyResolution.swift	64.71% <ø> (ø)
Sources/Spezi/Spezi/Spezi+Preview.swift	62.97% <0.00%> (ø)
Sources/XCTSpezi/Exports.swift	0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5adc30e...59033d3. Read the comment docs.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[PSchmiedmayer]

Thank you for all the work here!

Would be amazing to see if and how we can transition XCRuntimeAssertions to support Swift Testing to transition the remaining tests. I am wondering what a good approach around this would look like; I created SwiftTestingExtensions a while and am wondering if this should move in there and/or if we just rename/update XCRuntimeAssertions to also support Swift Testing in a nice way?

[Supereg]

Thank you for all the work here!

Would be amazing to see if and how we can transition XCRuntimeAssertions to support Swift Testing to transition the remaining tests. I am wondering what a good approach around this would look like; I created SwiftTestingExtensions a while and am wondering if this should move in there and/or if we just rename/update XCRuntimeAssertions to also support Swift Testing in a nice way?

I would probably rename XCTRuntimeAssertions to just RuntimeAssertions and make it support both XCTest and Swift Testing. Aiming to submit a PR for that soon.

[PSchmiedmayer]

Sound like a great idea!