Migrate to @_spi instead of @testable

[Supereg]

Migrate to @_spi instead of @testable

♻️ Current situation & Problem

Currently, we use @testable within XCTSpezi to access the internal interface of Spezi. This introduces complications for people using XCTSpezi. Using @_spi is also better as we have a reduced interface that we expose and even allow for others to leverage the same power when accessing the System Programming Interface.

⚙️ Release Notes

• Fixed an issue where compilation fails in certain test environments.

📚 Documentation

--

✅ Testing

--

📝 Code of Conduct & Contributing Guidelines

By submitting creating 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.

[PSchmiedmayer]

Sounds like a good approach to me; we will need to adjust the Swift Package tests accordingly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.97%. Comparing base (0ced3ef) to head (d698615).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   84.95%   84.97%   +0.02%     
==========================================
  Files          40       41       +1     
  Lines         950      951       +1     
==========================================
+ Hits          807      808       +1     
  Misses        143      143              

Files	Coverage Δ
Sources/Spezi/Module/ModuleCollection.swift	100.00% <ø> (ø)
...pezi/Spezi/KnowledgeSources/LaunchOptionsKey.swift	100.00% <ø> (ø)
Sources/Spezi/Spezi/Spezi.swift	96.67% <100.00%> (ø)
Sources/Spezi/Standard/DefaultStandard.swift	100.00% <100.00%> (ø)
Sources/XCTSpezi/DependencyResolution.swift	94.45% <ø> (ø)

---

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 0ced3ef...d698615. Read the comment docs.