Adds support for optional label in the checkbox component

[vraja-pro]

Context

Summary

This PR can be summarized in the following changelog entry:

• [@yoast/ui-library 0.1.0] Adds support for optional label for checkbox components.

Relevant technical choices:

• This PR is following the usage of the checkbox in Feature/get redirects #22356.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

For developers

• Run the storybook
• Smoke test the element "Checkbox"
• Check you see another story for "Without label"
• Check the documentation is clear.

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 ae9695c6802ca06686f786cc62d1c2381fc99b70

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 15 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.008%) to 53.661%

---

Files with Coverage Reduction	New Missed Lines	%
packages/js/src/introductions/initialize.js	6	0.0%
packages/js/src/introductions/components/content.js	9	0.0%

Totals
Change from base Build 3010e3277d95433295cd9d14a28c13715abc6a66:	-0.008%
Covered Lines:	30346
Relevant Lines:	57567

---

💛 - Coveralls

[igorschoester]

CR && AT ✅

Can merge, but two remarks:

1. A story where we mention adding aria-label instead of passing a label
2. You fixed the default argument and JSDoc for className, but the disabled is also missing 😇

Good to merge regardless, so leaving whether you want to do anything about the above to you.

[igorschoester]

CR && AT ✅

I think the lint failure is on trunk