Add yarn constraints rules requiring that dual CJS/ESM builds and type declarations be exposed for all export subpaths in package manifests

[MajorLift]

Descriptions

• Adapt these rules so that they are applied to all subpath exports, not just 'exports["."]'.
• Fix package manifests that violate the new rules.
  • https://github.com/MetaMask/core/blob/main/packages/notification-services-controller/package.json
  • https://github.com/MetaMask/core/blob/main/packages/profile-sync-controller/package.json

References

• Follow-up from Replace tsup with ts-bridge #4648
  • See Replace tsup with ts-bridge #4648 (comment)

[mcmire]

What should we check here? In the case of . we can reasonably expect that the output JS files are located at dist/index.mjs and dist/index.cjs and that the output declaration files are at dist/index.d.mts and dist/index.d.cts. However, that may not be the case for subpath exports, which may be in different directories. For instance, @metamask/notification-services-controller has a subpath export at ./notification-services/ui, and this points to the relevant files in dist/NotificationServicesController/ui.

Perhaps all we can check is the following?

• import.types ends in /index.d.mts
• import.default ends in /index.mjs
• require.types ends in /index.d.cts
• require.default ends in /index.cjs
• types are listed first in both import and require