Use NPM workspaces

[yusuke-omae]

What?

Enable npm workspaces.

Why?

npm workspace can detect incorrect management of monorepo.
This PR is a follow-up to #48950 and #53426.

How?

Testing Instructions

Testing Instructions for Keyboard

Screenshots or screencast

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: yusuke-omae <omaeyusuke@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: kevin940726 <kevin940726@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @yusuke-omae! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[gziolo]

@kevin940726, I see some Ci jobs failed. Do you remember what other changes were necessary to enable workspaces?

[kevin940726]

I don't recall exactly the parts needed, but I also don't remember having to change so many lines in package-lock.json 🤔. I think there might be something wrong there and maybe we could try regenerating them?

[gziolo]

The difference was that the local packages were still listed as dependencies in the package.json in the old PR:

I'm wondering how the changes proposed in this PR impact how dependencies get resolved. Do all of them get recognized as production or development dependencies? I also wonder what implications it has on how we scan licenses, as there is a more relaxed set of rules for dev dependencies.