Allow arbitrary catch clause type annotations

[jakebailey]

Fixes #20024

Playground

This is a follow-up to #52240 to exercise my comment in #52240 (comment), pulled into a PR for design meeting demoing.

The actual change is db0c9b0 (i.e. deletions only!), the rest is #52240 as it's not merged in main.

This probably conflicts with #13219 somehow, but I expect that the code in #52240 and this PR that grabs the type for the catch clause would just be updated. That or if we do something like #51390 this should still compose (as it's just another "default" implicit annotation).

[jakebailey]

@typescript-bot pack this

[jakebailey]

Weird:

We have no test that exercises this; I guess the catch clause isn't taking part in code flow, somehow.

It only happens in tsserver, though......

[jakebailey]

Semantic tokens! shakes fist

[jakebailey]

@typescript-bot pack this

[typescript-bot]

Heya @jakebailey, I've started to run the tarball bundle task on this PR at 4368a4a. You can monitor the build here.

[typescript-bot]

Hey @jakebailey, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/142987/artifacts?artifactName=tgz&fileId=8976A24C1A928E71502339E84B0A8225C82B23FFC1FE8203D30CA0E938C0815C02&fileName=/typescript-5.0.0-insiders.20230118.tgz"
    }
}

and then running npm install.

---

There is also a playground for this build and an npm module you can use via "typescript": "npm:@typescript-deploys/pr-build@5.0.0-pr-52280-7".;

[jakebailey]

I posted this because it was easy after #52240, but per design meeting it seems that this feature isn't palatable (which is totally fair!) especially in the context of upcoming ES pattern matching proposals; closing.