Disable "Generate 5 more" button only when limit reached and premium enabled.

[vraja-pro]

Context

Summary

This PR can be summarized in the following changelog entry:

• Disables "Generate 5 more" button only when limit reached and premium enabled.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Edit a post and use this patch on local environment:
  fake-api.patch
• Enable Premium.
• Click on "Use AI" and get to the point you can generate title/description.
• Check you reach the 10 spark limit.
• Check you can still click on the "Generate 5 more" button

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes #

[coveralls]

Pull Request Test Coverage Report for Build e360b3bed2bbc5193e2793a786b752dd56dd86e4

Details

• 0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.003%) to 52.041%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/js/src/ai-generator/components/modal-content.js	0	2	0.0%

Totals
Change from base Build d90c42d211eeafbbd4ae5f09cc5a6ba8c2675a3d:	-0.003%
Covered Lines:	29976
Relevant Lines:	58671

---

💛 - Coveralls

[igorschoester]

CR && AT ✅