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

この issue では、リポジトリのファイルやテストが指定されていません。まず #41016 で参照されている既存の catch 変数の変更を読み、次に Promise.catch のコールバックの挙動およびリンクされている eslint ルールと比較してください。これらのコールバック変数を unknown として型付けする、レビュー済みのフラグ設計と対応する実装およびテストが完成すれば完了です。