chore(wp-env): adds wp-env configuration for local development

[firestar300]

Adds a .wp-env.json file to define the plugins to be loaded during local development.

Updates package.json to include start:env and stop:env scripts for managing the local WordPress environment using wp-env.

Updates the node version to 22.22.0 in the volta configuration.

---

Note

Low Risk
Adds local dev configuration only; no runtime, data-handling, or security-sensitive code paths are changed.

Overview
Adds a .wp-env.json config to run the project plugin via wp-env for local WordPress development.

^{Written by Cursor Bugbot for commit 1d7ff46. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Config file name mismatches script reference path

High Severity

The newly created config file is named .wp-env.json (dot-prefixed hidden file), but the package.json scripts reference --config=./wp-env.json, where ./ is just a relative path prefix — meaning they look for a file literally named wp-env.json. These are two different filenames, so the start:env and stop:env scripts won't find this configuration. Either the --config flag needs to point to ./.wp-env.json, or the flag can be removed entirely since wp-env automatically discovers .wp-env.json by default.