Infer which files should SDKs include using manifest data

[clemyan]

What's the problem this PR addresses?

Some SDKs do not include all exposed files, making some features inaccessible to some editor integration. In particular, the ESLint SDK does not include lib/unsupported-api.js needed for its experimental flat config feature.

Closes #5231
Closes #5471

How did you fix it?

As outlined in #5231, the list of exposed files can be inferred by reading the main, bin, and exports fields of the manifest. This PR switches all existing SDK generators to doing so. Some SDKs (e.g. Typescript) still requires some special treatment so the PR keeps some escape hatches.

Questions

1. I don't know if this is considered a breaking change, I have marked @yarnpkg/sdks for a minor release for now.
2. typescript-language-server has not exposed a CJS entrypoint since 1.0.0, and as far as I know the SDK mechanism cannot support ESM files since loaders cannot be dynamically added once userland code starts execution. Should we just remove that SDK?
3. In the same vein, should we just ignore any conditional exports that require the import condition? .mjs files?

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[clemyan]

Any thoughts on the questions?

• I don't know if this is considered a breaking change, I have marked @yarnpkg/sdks for a minor release for now.
• typescript-language-server has not exposed a CJS entrypoint since 1.0.0, and as far as I know the SDK mechanism cannot support ESM files since loaders cannot be dynamically added once userland code starts execution. Should we just remove that SDK?
• In the same vein, should we just ignore any conditional exports that require the import condition? .mjs files?

[arcanis]

Any thoughts on the questions?

• I don't know if this is considered a breaking change, I have marked @yarnpkg/sdks for a minor release for now.
• typescript-language-server has not exposed a CJS entrypoint since 1.0.0, and as far as I know the SDK mechanism cannot support ESM files since loaders cannot be dynamically added once userland code starts execution. Should we just remove that SDK?
• In the same vein, should we just ignore any conditional exports that require the import condition? .mjs files?

Sorry, missed this notification

• It doesn't matter for @yarnpkg/sdks because dlx always pulls latest, which in the case of sdks is the current RC 😅
• There's now a register API to dynamically register loaders: register