* Add scopes for unary arithmetic operators (`+`, `-`)
* Ensure that function parameters set `capture.final`

…at ends of transactions — instead of falling back to a transaction-wide auto-indent quite so easily.

…but only while we can afford to spend time on re-parsing.

Synchronous indentation hinting is clearly the best choice, but it can theoretically be very costly. So we'll set a time budget per transaction — currently 10ms, but could be adjusted up or down. We'll start out doing synchronous indentation, but flip to async indentation if we run out of time in a given transaction. At the end of a transaction, the time budget resets.

This allows us to balance indentation accuracy with editor responsiveness, and would even allow us to expose this tradeoff as a setting in the future. The current threshold, 10ms, would probably result in one dropped frame if exceeded, but not two.

Right now, any one parse can exceed the budget — because we don't set a timeout on the parse the way we do with an async parse. But this could be changed in the future. The main goal here is to prevent a catastrophic scenario where a complex transaction locks up the editor.

…if the user has opted into them via _only_ a scope-specific setting.

* When set to `true`, `hideDuplicateTextMateGrammars` will hide all grammars except whichever one the user has indicated a preference for — via `useTreeSitterParsers` and `useLegacyTreeSitter` settings, whether global or scope-specific.

* When set to `false`, `hideDuplicateTextMateGrammars` will show all grammars, even Legacy Tree-sitter.

…to reflect new behavior of `GrammarRegistry#getGrammars`.

…when the user's preferred type of grammar isn't available for a particular language.

…when `hideDuplicateTextMateGrammars` is `false`.

…in a macro definition.

Fixes pulsar-edit#945.

…when `prefillSelectedText` is `true` and the editor has selected text when a `SelectListView` is opened.

* GOTO labels
* Members like `foo.bar`
* Marking of constants in C++