Packages: Fix all missing or obsolete dependencies in packages

[gziolo]

Description

I discovered that we have some differences in the list of dependencies for WordPress packages. In particular, I have some issues integrating all recently published npm packages with WordPress core. Related ticket:
https://core.trac.wordpress.org/ticket/47843

How has this been tested?

In general, on Gutenberg side, it all should be transparent as we have build tools which properly generate dependencies consumed by WordPress. In core, we have to do it manually so that might be why it doesn't quite work as necessary.

[gziolo]

@hypest and @koke - I disabled native files for now to fix all the issues which web version has, but we definitely should revisit it really soon.

[gziolo]

there is a follow-up: #16978

[ellatrix]

I wonder if there's any way we can check the JS files for imports and error if the dependency is not found in the package.json file, and also error if there are dependencies that are listed and not used.

[gziolo]

I wonder if there's any way we can check the JS files for imports and error if the dependency is not found in the package.json file, and also error if there are dependencies that are listed and not used.

So this new ESLint rule (import/no-extraneous-dependencies) I added in this PR solves the first case :)
I couldn't find anything which covers 2nd scenario.

[ellatrix]

I couldn't find anything which covers 2nd scenario.

How did you know which dependencies to remove then?

[ellatrix]

Awesome!

[gziolo]

I couldn't find anything which covers 2nd scenario.

How did you know which dependencies to remove then?

It was a manual process. I went through build folder where we have JSON files generated with dependencies for each module which are used in the code. Based on that, I removed those WP packages which weren't listed. It would be great to have this automated with a linter rule.