Release `yoastseo` and preview packages to NPM

[d-claassen]

[!IMPORTANT] Do not rebase this PR. The "Version increase" commit fa68e4c11e8977c5df5e3c1a08976c847a914be8 is the exact version that has been published to NPM. Orphaning this commit will make it impossible to properly determine changes since the published version.

Context

• Release our YoastSEO.js and preview packages to NPM again for easier reuse:

• @yoast/components:3.0.0-alpha.0
• @yoast/feature-flag:0.6.0-alpha.0
• @yoast/helpers:0.17.0-alpha.0
• @yoast/replacement-variable-editor:2.0.0-alpha.0
• @yoast/search-metadata-previews:3.0.0-alpha.0
• @yoast/social-metadata-forms:2.0.0-alpha.0
• @yoast/social-metadata-previews:2.0.0-alpha.0
• @yoast/style-guide:0.14.0-alpha.0
• yoastseo:2.0.0-alpha.0

Summary

This PR can be summarized in the following changelog entry:

• Release new package versions.

Relevant technical choices:

• went with premajor version increases because of (at least) the change to a transpiled published package. Major version zero packages went to 0.x.0-alpha.0 and the rest to x.0.0-alpha.0
• focused on @yoast/search-metadata-previews and @yoast/social-metadata-previews for now with all sub-dependencies
• remove side-effect of publish, as per the recommendation in https://yarnpkg.com/advanced/lifecycle-scripts
• use files to determine what we would publish, see https://docs.npmjs.com/cli/v10/configuring-npm/package-json#files
• ignore .map files, in case the build contains them
• move @yoast/browserslist-config's index.js out of src folder, for convenience of no src in the published version (there's no build step that introduces a build folder)
• cascade the peer dependency for the packages using @yoast/replacement-variable-editor

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

All changes in this PR are related to what we publish to NPM (which isn't used by any plugin). So this shouldn't effect the plugin itself at all. Any regression testing should be focused on JavaScript-powered features, and specifically those features provided by our NPM packages.

• Regression test the social & search previews in the metabox and sidebars. Test both with Free and Free+Premium.
• Regression test the "insights" section of the metabox and sidebars. Verify all @yoast/components look as before.
• Regression test the SEO/readability/inclusive language analyses.
• Regression test the replacement variable editors in the Yoast SEO settings.

Relevant test scenarios

• [x] Changes should be tested with the browser console open
• [ ] Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• [x] 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

• [x] QA should use the same steps as above.

Impact check

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

• All changes in this PR are related to what we publish to NPM (= a version of the packages not used by any plugin). So this shouldn't effect the plugin itself at all. Any regression testing should be focused on JavaScript-powered features, and specifically those features provided by our NPM packages.

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 #