Multi tiers upgrade feature - Base PR

[wordpressfan]

Description

Fixes https://github.com/wp-media/wp-rocket.me/issues/4326

Explain how this code impacts users.

Type of change

• New feature (non-breaking change which adds functionality).

Detailed scenario

Everything is mentioned in the issue, the service team changed the API to return the available upgrades and we used that without doing any calculations on the plugin side.

Technical description

Documentation

Everything is mentioned in the issue and sub-issues.

New dependencies

Now we depend on the new API, so we need to make sure that we release the API to the production site one day before releasing this change in plugin because we save the user API for one day.

Update: Now we have the API changes live.

Risks

We need to validate also the upgrade process with older versions of the plugins to make sure they are working.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

If some mandatory items are not relevant, explain why in this section.

Additional Checks

• In the case of complex code, I wrote comments to explain it.
• When possible, I prepared ways to observe the implemented system (logs, data, etc.).
• I added error handling logic when using functions that could throw errors (HTTP/API request, filesystem, etc.)

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 9acceae1	✅ 90.48% (target: 50.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (9acceae)	Report Missing	Report Missing	Report Missing
Head commit (d11aced)	38231	16727	43.75%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#7197)	84	76	90.48%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[Mai-Saad]

@wordpressfan Thanks for the PR.
Note:

• the arrow in the upgrade button is small and not centralized
• the selected option in multi can be highlighted when open the dropdown
  will leave it to @wp-media/product to share reference UI
  @marija-nikolic Please check the UI of different forms
  Upgrade from multi 100
  

upgrade from multi 50

upgrade from growth

upgrade from single

No upgrade for multi500

[Mai-Saad]

Promo banner
for single

for plus

for growth

for multi 50

for multi100

multi 500, no promo

[marija-nikolic]

Congrats, team, everything seems good to me. 👏
I agree with what @Mai-Saad wrote:

• the arrow in the upgrade button is small and not centralized
• the selected option in multi can be highlighted when open the dropdown

Only one small thing: it should be written Growth or Multi on the yellow banner:

[Mai-Saad]

testrail-report-676.pdf

[Khadreal]

Screenshot

Fixed the copy on the yellow banner

Aligned arrow

cc @Mai-Saad, @marija-nikolic

[marija-nikolic]

Screenshot

Fixed the copy on the yellow banner Aligned arrow

cc @Mai-Saad, @marija-nikolic

Thanks, looks good.

[wordpressfan]

So we are fine here, thanks @Khadreal @marija-nikolic @Mai-Saad

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 9acceae1	✅ 90.48% (target: 50.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (9acceae)	Report Missing	Report Missing	Report Missing
Head commit (35a3a06)	38231	16727	43.75%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#7197)	84	76	90.48%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩