feat(errors): validate preset when filename is absent

[JLHwung]

Closes #10154

Q	A
Fixed Issues?	Fixes #10154
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?	Yes
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?	No
License	MIT

Validate preset before buildPresetChain, when it is the last chance we can get the UnloadedDescriptor and include preset name in error message. We may add more business logic inside validatePreset to print preset-specific error message.

I have also considered the following alternative designs:

1. Pass down descriptor name to matchPattern.
   Pro: The missing filename errors are still thrown in matchPattern
   Cons: Introduce unnecessary signature complexity as this is not our primary execution path

2. Add descriptor name to ConfigContext
   Pro: The missing filename errors are still thrown in matchPattern
   Cons: ConfigContext has to be mutated or cloned when running buildPresetChain. The ConfigContext is widely used across config chain building but descriptor name is only used to print this error.

3. tryCatch buildPresetChain
   Pros: Intuitive and fewer execution path
   Cons: Any error from buildPresetChain has to be matched once before they are re-thrown.

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/11468/

[existentialism]

Might be nice to link directly to the option:

Preset ${name} requires a filename be set. See https://babeljs.io/docs/en/options#filename.

Or even:

Preset ${name} requires a filename be set. For example, if you are calling Babel directly:

babel.transform(code, { filename: 'file.js', presets: [${name || '/* your preset */'}] });

See https://babeljs.io/docs/en/options#filename for more information.

(And, as you mentioned, improve this later with user- and preset-specific messages)

[JLHwung]

That delivers way better dev UX. Addressed in cf0f27a.

[existentialism]

Should we also update the language on the options page (https://babeljs.io/docs/en/options#filename)?

Maybe simply changing:

The filename is exposed to plugins. Some plugins may require the presence of the filename.

to:

Some presets and plugins may require the presence of the filename.

Or, since we get the question a bunch, call out preset-typescript's behavior directly here?

(We can continue discussion on the website repo after this lands)

[nicolo-ribaudo]

We should also check if the overrides option contains a block which has one of these three options (like in the TS preset).

[JLHwung]

Good catch. Fixed in 056e197.

[nicolo-ribaudo]

(Note: I labeled this as "New feature" but I I think that this PR can be merged in a patch version)

[JLHwung]

I read again and feel like

Preset ${formattedPresetName} requires a filename to be set when babel is called directly,
`\`\`\``,
`babel.transform(code, { filename: 'file.ts', presets: [${formattedPresetName}] });`,
`\`\`\``

And we may can change file.js to file.ts since this is the popular path.

[nicolo-ribaudo]

And we may can change file.js to file.ts since this is the popular path

Good idea