Flag to type `Promise.catch` variables as `unknown`

Suggestion

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Following #41016 a flag was added to consider catch variables as unknown.
For consistency and since they're similar cases, I suggest also adding a flag that does this for .catch callbacks on promises.

See also: eslint-plugin-etc/no-implicit-any-catch

Das Issue nennt keine Repository-Dateien oder Tests. Lies zunächst die in #41016 referenzierte Änderung an catch-Variablen und vergleiche sie anschließend mit dem Verhalten von Promise.catch-Callbacks und der verknüpften eslint-Regel. Erledigt ist die Aufgabe, wenn ein geprüftes Flag-Design sowie die entsprechende Implementierung und Tests vorhanden sind, die diese Callback-Variablen als unknown typisieren.