refactor: create WireAuthentication feature module

[johnxnguyen]

Issue

Initial ideas for a WireAuthentication feature module that would contain the whole login and registration flow.

---

Checklist

• Title contains a reference JIRA issue number like [WPB-XXX].
• Description is filled and free of optional paragraphs.
• Adds/updates automated tests.

---

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

• Make sure you use the API for UI elements that support large fonts.
• All colors are taken from WireDesign.ColorTheme or constructed using WireDesign.BaseColorPalette.
• New UI elements have Accessibility strings for VoiceOver.

[github-actions]

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit d47cbb5.

[johnxnguyen]

I think it could be a good practice to always mark the invoke method as @MainActor because:

1. It creates a cleaner call side from the view model which should also be main actor isolated (i.e just create a Task and run the use case.
2. It makes it explicit to the implementation on which thread the use case is being called on and therefore the responsibility of the implantation to manage efficient concurrent execution.

[caldrian]

Will there be more code than the assembly in the entry point target?
If not, isn't it a bit too much of an overhead to have a separate target?

[johnxnguyen]

I don't think there would be anything other than instantiating components, wiring them together and returning them. Where would be another place to put it if we don't have a separate target? It couldn't exist inside either the UI or Core targets because the assembly needs to combine components from both.