Simplifies setData extensions

[vishnuravi]

Simplifies setData extensions

♻️ Current situation & Problem

This setData extensions can be simplified to remove the continuations as the Firebase SDK now provides an async function for saving a dictionary to Firestore. This may also resolve the bug reported in #37, as the continuation is now removed.

⚙️ Release Notes

Updates the setData extensions to use the async function as described above.

📚 Documentation

The function signatures are unchanged and no changes to documentation are required.

✅ Testing

Additional tests have been added.

📝 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.

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 63.02%. Comparing base (00ff0db) to head (fe55d5b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
+ Coverage   61.39%   63.02%   +1.63%     
==========================================
  Files          19       19              
  Lines        1155     1122      -33     
==========================================
- Hits          709      707       -2     
+ Misses        446      415      -31     

Files	Coverage Δ
.../SpeziFirestore/DocumentReference+AsyncAwait.swift	58.34% <66.67%> (+30.27%)	⬆️

---

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 00ff0db...fe55d5b. Read the comment docs.

[PSchmiedmayer]

Nice, looks good to me; thank you @vishnuravi for the simplification here!

[PSchmiedmayer]

Thank you @vishnuravi for the added tests!

[Supereg]

Was there any more detail why this crash occurred. Particularly the crash message would be interesting.
I'm currently trying to make these methods concurrency safe and easiest solution would be to bring back the continuation-based approach of wrapping the Firebase setData(from:encoder:completion:) methods. This ensures that the from argument never leaves the isolation from the caller. Currently it does which might introduce race conditions or requires the type to conform to Sendable.
Another solution would be to inherit isolation (see SE-0420). However then sending the encoded dictionary produces currently a Sendable warning.