fix: Resolve CI test failures (MySQL container + Jest compatibility)

[josephfusco]

This pull request introduces several improvements and updates to the testing configuration, dependency management, and CI workflow for the project. The main focus is on modernizing Jest configurations for ESM support, updating dependencies, refining test assertions, and optimizing CI scripts for reliability.

Testing configuration and dependency updates:

• Updated Jest configurations in packages/blocks/jest.config.js, packages/faustwp-cli/jest.config.js, and packages/faustwp-core/jest.config.js to use ESM support via ts-jest, removed redundant globals entries, and switched coverage provider to v8 for better performance and compatibility. Coverage collection is now disabled by default. [1] [2] [3] [4] [5] [6]
• Updated dev dependencies in packages/blocks/package.json and packages/faustwp-core/package.json, including upgrading ts-jest to version ^29.1.1 and adding missing Jest-related type dependencies. [1] [2]

Test improvements and snapshot updates:

• Refactored test assertions in packages/faustwp-core/tests/components/Toolbar/Toolbar.test.tsx to use direct array equality instead of inline snapshots for improved clarity and maintainability. [1] [2] [3] [4] [5] [6] [7]
• Updated snapshot files and assertions for sitemap and environment variable validation tests to ensure consistency with new output formats and assertion styles. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Continuous Integration workflow improvements:

• Improved database readiness checks in GitHub Actions workflows by switching to use docker compose exec for MySQL ping, ensuring more reliable DB startup in both nightly and regular plugin unit test jobs. The working directory is now explicitly set for these steps. [1] [2]

Miscellaneous:

• Removed the redundant version declaration from the top of plugins/faustwp/docker-compose.yml to align with current Docker Compose best practices.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d26173e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	278.08 KB (🟡 +11.71 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/example	807 B	278.87 KB	79.68% (+/- <0.01%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.