…and out of `WASMTreeSitterLanguageMode` for reasons of encapsulation.

Fixes issue with parsing of selectors in `:has`, `:is`, and other pseudoclasses.

…including more consistent firing of the `did-suggest-indent` event.

…and fix a bug with the indentation reparse budget.

…as booleans. Handle `NULL` in a similar way.

…and update our API usages.

Tree-sitter harmonized the API differences between `web-tree-sitter` and
`node-tree-sitter` in version 0.22.0. This is the first time we’ve had to deal
with that. Luckily, the changes were mostly palatable.

The biggest API difference is in `Query#captures`; two positional arguments for
defining the extent of the query have been moved to keyword arguments. We’ve
updated our internal usages, but any community packages that relied on the old
function signature would break if we didn’t do anything about it. So we’ve
wrapped the `Query#captures` method in one of our own; it detects usages that
expect the old signature and rearranges their arguments, issuing a deprecation
warning in the process. Hopefully this generates enough noise that any such
packages understand what’s going on and can update.

Other API changes are more obscure — which is good, because we can’t wrap them
the way we wrapped `Query#captures`. They involve conversion of functions to
getters (`node.hasErrors` instead of `node.hasErrors()`), and there’s no good
way to make both usages work… short of wrapping nodes in `Proxy` objects, and
that’s not on the table.

Since lots has changed in `tree-sitter` since we last upgraded
`web-tree-sitter`, I updated our documentation about building a custom version
of `web-tree-sitter`.

…only injections with a shallower depth.

…and modify query files in response to all non–backwards-compatible changes.

…after `tree-sitter-javascript` bump.

…to conform to new `tree-sitter-(java|type)script` node structure for template strings.

…at new repo location.

…for `tree-sitter-html` and `tree-sitter-embedded-template`.

Fixed an inscrutable out-of-memory error I was getting in an EJS file.

…related to updating open documents’ syntax highlighting as grammars are processed.