[VIO-129] feat: Extract Lock related screens from router

The Lock related screens are responsible to lock the app when it goes to OS background and to display a CTA to the user when their phone is not protected

Previous implementation declared those screens inside of the App's router

This had numerous caveats:

It was difficult to keep track of when the app would need to be locked
It was difficult to keep track of where the user was before the app being locked
- For example we needed to wait for the HomeView to be initialized and check if a cozy-app or the OSReceive screen should be displayed to give it to the Lock screen as a context (cf here)
It was difficult to keep track of when hiding the splashscreen
If a component was calling navigate() in reaction of an event while behind the lock screen then the app would leave the lock screen
- For example this occurred in OauthClientsLimitService when the following conditions were met:
- the OAuth client limit was exceeded
- the default app was a cozy-app
- the app was configured to display the lock screen
We had to rely on some tricks to ensure the navigation to be done on HomeScreen first and then on the Lock screen so the HomeScreen's webview can start loading while the user enters their credentials
In some situation, the Lock screen was impacted by re-renders of the app
- This was visible when the Biometry was triggered on iOS. Sometime it would appear 2 times, sometimes it would directly dismiss with the following error in the console: Canceled by another authentication

This PR removes those screen outside of the router

With the new implementation, those screen are now displayed on top of the UI without interaction with the router

This allow the application to live behind the Lockscreen, so:

The HomeScreen is, by default, pre-loading behind the lock screen
If the app should start on the HomeScreen, on an AppScreen, or on the OSReceiveScreen has no impact anymore on the LockScreen flow
There is no need to track where the user was, when hiding the lock screen, the app is already where it was before displaying the lock screen
There is no risk to have navigate() collision anymore, the app can do navigation in background based on events and this won't affect the fact that the Lock screen is always displayed until the user enters their credentials
The Lock screens are rendrered in parallel of the <App /> component, so there should be no risk of rerender side effects between each-other

TODO:

[x] clean remaining trace of security flow in HomeView (hasRenderedOnce ref, useEffect name and logs)
[x] fix unit tests

cozy / cozy-flagship-app

[VIO-129] feat: Extract Lock related screens from router #1092