Issue/12494 blaze webview fragment

[JorgeMucientes]

Closes: #12494 and #12547

Description

This PR adds 3 things:

• Creates a new campaign detail webview to handle actions over the campaign.
• Refreshes Blaze campaign list when coming back from campaign detail webview and the campaign has been stopped/cancelled
• Triggers Blaze native flow when user clicks on "Promote again" CTA

Testing information

1. Log into a site with Blaze enabled
2. Create a Blaze campaign
3. From Blaze campaign list screen, click on the active campaign you've just created and Stop/Cancel it.
4. Navigate back and check how the campaign list is updated with the most recent status updates
5. Click again on any campaign from the list.
6. From the campaign detail webview click on "Promote again" CTA
7. See how the native campaign flow is triggered for the same product.

The tests that have been performed

• Tested Blaze campaign list refreshes correctly
• Tested promote again CTA triggers Blaze campaign creation.

Images/gif

demo.mp4

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

Reviewer (or Author, in the case of optional code reviews):

Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement:

• The PR is small and has a clear, single focus, or a valid explanation is provided in the description. If needed, please request to split it into smaller PRs.
• Ensure Adequate Unit Test Coverage: The changes are reasonably covered by unit tests or an explanation is provided in the PR description.
• Manual Testing: The author listed all the tests they ran, including smoke tests when needed (e.g., for refactorings). The reviewer confirmed that the PR works as expected on big (tablet) and small (phone) in case of UI changes, and no regressions are added.

[dangermattic]

	3 Warnings
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.
⚠️	Class ViewState is missing tests, but unit-tests-exemption label was set to ignore this.
⚠️	This PR is assigned to the milestone 20.6. This milestone is due in less than 2 days. Please make sure to get it merged by then or assign it to a milestone with a later deadline.

Generated by 🚫 Danger

[wpmobilebot]

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

	App Name	WooCommerce-Wear Android
	Platform	⌚️ Wear OS
	Flavor	Jalapeno
	Build Type	Debug
	Commit	fbb92ac
	Direct Download	woocommerce-wear-prototype-build-pr12648-fbb92ac.apk

[wpmobilebot]

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

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Commit	fbb92ac
	Direct Download	woocommerce-prototype-build-pr12648-fbb92ac.apk

[JorgeMucientes]

While I added unit test to the new viewModel, the lint checks still fail stating the following:

[2024-09-23T10:35:22Z] Errors:
--
[2024-09-23T10:35:22Z] - [ ] Please add tests for class `ViewState` (or add `unit-tests-exemption` label to ignore this).

That doesn't make sense, so I'm adding the unit-tests exemption tag to the PR

[hichamboushaba]

That doesn't make sense, so I'm adding the unit-tests exemption tag to the PR

Yes, that's what I would do to, adding unit tests for a plain class like the ViewState shouldn't be needed.

[hichamboushaba]

Nice work @JorgeMucientes, it works well, I left a minor suggestion, but it's not a blocker.

[hichamboushaba]

minor, I would suggest caching the results of blazeUrlsHelper.buildCampaignsListUrl() and blazeUrlsHelper.getCampaignStopUrlPath(navArgs.campaignId) and use the cached values instead of calling the functions here again and again, the onUrlLoaded will be called quite often.

[JorgeMucientes]

Good suggestion. Applied!