Report invalid `module` field in `package.json`

Some packages define the top-level `module` field in `package.json`. Although it’s non-standard, bundlers use it. This can lead to differences between usage in the browser and Node.js, but it is not possible to add type definitions for it.

I think it would be useful to report the `module` field if it does not match the `import` condition in the `package.json` `exports` field nor the `main` field.

For example:

- [`monaco-editor`](https://github.com/microsoft/monaco-editor/blob/main/package.json#L34)
- [`vscode-json-languageservice`](https://github.com/microsoft/vscode-json-languageservice/blob/main/package.json#L7)
- [`vscode-uri`](https://github.com/microsoft/vscode-uri/blob/main/package.json#L8)
- [`whatwg-fetch`](https://github.com/JakeChampion/fetch/blob/master/package.json#L6)

Empieza rastreando cómo se analizan los metadatos de package.json, centrándote en el campo module, la condición de importación de exports y el campo main descritos aquí. Se considera terminado cuando se informan los paquetes en los que module no coincide con esos campos; los paquetes de ejemplo indicados son útiles para comprobar el comportamiento.

Escrito por el modelo de indexación a partir del texto del issue.