chore: Fix notifications registration

[LouisCAD]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
24 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR fixes notification registration wiring for the standard flavor by ensuring notification-related components are initialized/registered early enough during app startup and by adding the required flavor-specific manifest entries.

Changes:

• Initialize userDataCleanableList in MainApplication’s init block (instead of onCreate) so it’s available earlier in app lifecycle.
• For the standard flavor, extend userDataCleanableList with NotificationsRegistrationManager in StandardMainApplication’s init block.
• Add a standard-source-set AndroidManifest.xml to register the flavor-specific AuthenticatorMessagingService and override the Application class.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
app/src/standard/kotlin/com/infomaniak/auth/StandardMainApplication.kt	Moves NotificationsRegistrationManager registration to app init time for the standard flavor.
app/src/standard/AndroidManifest.xml	Adds standard-flavor manifest overlay to register the FCM messaging service and set the flavor Application class.
app/src/main/kotlin/com/infomaniak/auth/MainApplication.kt	Initializes userDataCleanableList earlier (in init) to ensure it’s available before DI consumers may access it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.