Yarn 4 removed pre- and post- lifecycle scripts: https://yarnpkg.com/advanced/lifecycle-scripts

* remove side-effect of publish, as per the recommendation in https://yarnpkg.com/advanced/lifecycle-scripts
* using files determine what we would publish, see https://docs.npmjs.com/cli/v10/configuring-npm/package-json#files
* ignore .map files, just in case the build contains them
* move browserslist-config index out of `src` folder, just for convenience of no `src` in the published version

Tweak lint to use .eslintignore file instead of only running in the src and tests folders

Move lint ignore to separate file

* upgrade @wordpress/components to WP 6.4 version, fixes a test failing on UUID sub dependency having require
* move lint ignore to separate file

* add own config
* auto-fix comma-dangle

* add own config
* auto-fix comma-dangle

* rename clean:build to clean, inline with the other packages
* prefix node commands with yarn, as per their recommendedation when using PnP linking mode: https://yarnpkg.com/migration/pnp#enabling-yarn-pnp
* switch to lint all vs just src (ignore missing test deps)
* add missing jest jsdom, even though tests are disabled

* introducing ignore file
* tune the max warnings to the current number

* move to JS format
* remove exceptions
* change react to detect
* add css/dist/ to ignore list
* auto-fix comma-dangle

* starting with the upgrade in our jest-preset
* upgrade the other packages to match
* fixes needed, coming in next commits

* an error would result in an infinite loop: add url = false
* an error would not result in the error being displayed: add wait for next cycle
* the above fixes the indexation tests

* missing act
* the closing would result in further state changes that were not captured by the fireEvent.click
* solution: wrap next check in waitFor

* remove the UI library source from the module mapping, it is expected to run build before test instead
* remove different node_module overrides
* add WP i18n to the module mapping to ensure a singleton, this fixes the text-domain warnings

* see https://lerna.js.org/docs/concepts/task-pipeline-configuration
* upgrade lerna
* ran lerna repair
* specify ignore cache in grunt tasks, just to ensure no change there
* add clean task (handy for cache busting too)
* alphabetize scripts

* skipping preset upgrades - lets not require minor upgrades
* feature-flag: remove unused babel plugins

* align versions
* fix missing tailwindcss in root
* fix wrong tailwindcss/forms version (not as per postcss-preset requirement)

* remove unused from JS
* add missing webpack peer dep to UI lib

* move to actual deps: @yoast/helpers and styled-components
* remove unused json dep
* add peer deps: react and react-dom
* add browserslist config to extend the yoast config

* @reduxjs/toolkit requires react-redux 7 or 8
* react-redux 8 requires redux 4
* remove redux-thunk and unused script that was using it

* add react and react-dom to root, to satisfy peer deps
* remove unused @testing-library/react-hooks, warned about wanting older version of react-renderer (16.9.0 or 17.0.0 vs actual 18.2.0)

* as peer deps of the packages using replacement-variable-editor

* required by grunt-contrib-clean, grunt-shell and grunt-git
* update grunt-git to work with grunt 1.6.1

* because it supports React 18
* turns out the close on click outside error is fixed too:
* removing shouldCloseOnClickOutside false for: SearchAppearanceModal, SocialAppearanceModal, SEMrushRelatedKeyphrasesModal, WincherSEOPerformanceModal (Elementor) and InsightsModal (Elementor)

* not using React 18 (but 16 at the latest)

* inactive package since 5 years
* still requiring React 16.3.x
* moving over to already used WP a11y' speak
* adding a hook and wrapper component for ease of use, as per downside of original PR: #19615

* due to warning about React 18 (package was using 17 before)

* was requiring old React version (via react-test-renderer)
* not really used at the moment

(or packages provided by WP)
* trigger was some requiring older React version -- not totally solved yet:
  * WP components at WP 6.5 version will solve Reakit
  * WP block-editor still requires react-autosize-textarea, which is archived since March 1, 2024
  * WP compose and WP data still use use-memo-one 1.1.2 or 1.1.1 where 1.1.3 has React 18 support
* we are not providing these packages in our plugin, so this is only affecting testing and development

* no more transform ignore or mapping of Yoast packages or lodash-es
* remove unused find-with-regex
* fix test import of lodash-es to use lodash

* they are required as peer deps by @yoast/style-guide now
* and it makes a bit more sense that it is actually used, even though it is mostly indirectly via WP element

* using versions from @yoast/grunt-plugin-tasks range to prevent potential problems
* fixing version of @yoast/grunt-plugin-tasks

There are no tests in the root folder