[Jetpack Plugin Install] Reuse the tweaked UI for remote Jetpack install

[thomashorta]

Fixes #18045

Update the existing "Remote Install" Flow to use this same updated flow (made with Compose). This flow is triggered when the user clicks a Jetpack feature (such as Stats) without having the Jetpack plugin installed on their self-hosted site.

Demo

Success Flow

issue-18045-jp-install-remote-success-blur.mov

Error Flow

issue-18045-jp-install-remote-error.mp4

To test

Set up a self-hosted site that has only no Jetpack plugins at all.

1. Install Jetpack OR WordPress app
2. Login using the site credentials
3. Select the self-hosted site from the site list
4. Tap a Jetpack feature, such as Stats
5. Testing the error state
   1. Turn on Airplane mode
   2. Start the Plugin Install Flow
   3. Verify the UI is updated according to expectations
6. Testing the install flow
   1. Close the Plugin Install flow
   2. Turn off Airplane mode
   3. Tap a Jetpack feature, such as Stats
   4. Start the Plugin Install Flow
   5. Verify the UI is updated according to expectations
   6. Verify everything worked and the Jetpack plugin was installed

Regression Notes

1. Potential unintended areas of impact
   Changes in installation behavior.

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   Manual test (it is working exactly as it was before).

3. What automated tests I added (or what prevented me from doing so)
   Updated existing tests.

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[wpmobilebot]

📲 You can test these changes on Jetpack by downloading jetpack-installable-build-pr18058-d8c78c8.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	Jetpack
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	d8c78c8

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[wpmobilebot]

📲 You can test these changes on WordPress by downloading wordpress-installable-build-pr18058-d8c78c8.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	WordPress
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	d8c78c8

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[wpmobilebot]

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

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr18058-820cc08
	Commit	820cc08
	Direct Download	wordpress-prototype-build-pr18058-820cc08.apk

Note: Google Login is not supported on these builds.

[peril-wordpress-mobile]

	Warnings
⚠️	This PR is assigned to a milestone which is closing in less than 4 days Please, make sure to get it merged by then or assign it to a later expiring milestone
⚠️	PR has more than 300 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS

[wpmobilebot]

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

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr18058-820cc08
	Commit	820cc08
	Direct Download	jetpack-prototype-build-pr18058-820cc08.apk

Note: Google Login is not supported on these builds.

[RenanLukas]

Thanks for the changes, @thomashorta

It works as expected. I've left a question, but LGTM

[RenanLukas]

💡 Would it make sense to move this if and the trackWithSource call to the ViewModel?

[thomashorta]

I think it will not make a lot of difference in the code here as I still need to return some information saying the back should be blocked, but it's better in terms of testing the analytics. I will do the change.

[RenanLukas]

LGTM