Exclude string type annotations from ESP

[yilei]

Description

This PR excludes string type annotations from ESP, and also fixes crash on mismatched brackets from ESP.

1. Unfortunately pyright doesn't support stringified annotations that span multiple lines, e.g.:

def something(
    arg,
) -> (
    "VeryLongClassNameWithAwkwardGenericSubtype[int] |"
    "VeryLongClassNameWithAwkwardGenericSubtype[str]"
):
    ...

Even though other type checkers (mypy, pytype, pyre) do support them. To be safe, we can choose to exclude them from ESP for now. Note we could technically choose to try merging them into a single string when the result fits in the line-length, but this would be more complicated than simply excluding them from ESP.

2. The crash is because of unmatched brackets. In ESP, it can process lines continued from earlier line breaks, e.g.:

def something(
    arg,
) -> "VeryLongClassNameWithAwkwardGenericSubtype[int] | VeryLongClassNameWithAwkwardGenericSubtype[str]":
    ...

The line can be ) -> "VeryLongClassNameWithAwkwardGenericSubtype[int] |VeryLongClassNameWithAwkwardGenericSubtype[str]": while processing. This PR makes BracketTracker.mark accept unmatched closing brackets.

Fixes #3435. Fixes #3457.

Checklist - did you ...

• Add an entry in CHANGES.md if necessary?
• Add / update tests if necessary?
• Add new / update outdated documentation?

[github-actions]

diff-shades reports zero changes comparing this PR (926bdd1) to main (9ce7572).

---

What is this? | Workflow run | diff-shades documentation

[JelleZijlstra]

Thanks!