Remove aria label required to have the flexibility not to use the tooltip

[vraja-pro]

Context

• We want to make the aria label not required to have the flexibility not to use the tooltip. Related to Disable all AI buttons other than the one currently in use

Summary

This PR can be summarized in the following changelog entry:

• Allow the AI button to be used without tooltip.

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:

• Create a post with content and focus keyphrase.
• Make sure the introduction doesn't contain the focus keyphrase.
• Make sure the SEO assessments has also the sparkle for keyphrase density and distribution.
• Click on the sparkle button in the AI assessment fix for keyphrase in introduction.
• Check the rest of the ai sparkle buttons are disabled and when hovering them you see no tooltip.
• Open dev tool console and check you do not get any console error that ariaLabel prop is required.

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

[github-actions]

@vraja-pro Please be aware that following packages have been abandoned and are not actively maintained anymore:

Package name	Path
@yoast/babel-preset	packages/babel-preset
@yoast/components	packages/components
@yoast/e2e-tests	packages/e2e-tests
@yoast/helpers	packages/helpers
@yoast/jest-preset	packages/jest-preset
@yoast/style-guide	packages/style-guide

Please consider using the other packages instead.

[coveralls]

Pull Request Test Coverage Report for Build 705999af5d61801c4c3617040870823aca48d7c4

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 48.696%

---

Totals
Change from base Build 8fb173ff8ff2ae2dd79ba06711e9f5fc2e9db948:	0.0%
Covered Lines:	25253
Relevant Lines:	53697

---

💛 - Coveralls

[mhkuu]

LGTM! 🎉