Properly init in-memory usage when restoring the state

[AdamGrzybkowski]

Closes #609

Description

When the "Don't keep activities" is ON, the Quick Editor state won't properly display the data inside. It's caused by a timing issue. The QuickEditorContainer.getInstance().useInMemoryTokenStorage() that is called in the DisposableEffect is invoked after the NavController starts the restored destination, so the ViewModel and its dependencies don't use the in-memory storage as they should.

Moving the DisposableEffect to a Composable higher up in the hierarchy fixes this timing issue.

Before	After

Testing Steps

1. Enable Developer Options on your device
2. Launch the demo app
3. Move to the Avatar update tab
4. Paste in your WP token and select the checkbox next to it. You can also add it to secrets.properties file with name demo-app.bearer.token.
5. Tap the avatar to launch the QE
6. Tap on the View Profile
7. Go back with a system button or a gesture
8. Confirm the QE is restored and no errors are visible

[wpmobilebot]

📲 You can test the changes from this Pull Request in Gravatar Demo by scanning the QR code below to install the corresponding build.

	App Name	Gravatar Demo
	Commit	78837cc
	Direct Download	gravatar-demo-prototype-build-pr610-78837cc.apk

[etoledom]

I was able to reproduce the issue in trunk, and these changes fixes it 🎉

I also saw another problem where the profile card wasn't showing when opening the QE with a given token, but this also seem to have been fixed with these changes.

This last issue I wasn't to reproduce it again in trunk, so I can't get a video now.