Upgrade tree-sitter dependencies

[latin-panda]

Description

Upgrade all dependencies related to tree-sitter in the project to their latest compatible versions. Ensure the following requirements are met:

1. Address any conflicts that arise during the upgrade process.
2. Update the expected version variable to reflect the new tree-sitter version.
3. Ensure the bundle size does not increase, as tree-sitter already contributes significantly to the bundle size.
4. Verify that no new unnecessary build artifacts are introduced (reference: build script).
5. Confirm that all scenario tests pass successfully.
6. Verify that performance is unchanged or improved compared to the current implementation.

[garethbowen]

I've been having a look at this but haven't gotten very far, but wanted to document my progress.

After updating I found the exported types had changed so needed some code changes. Now when running the tests I'm hitting some issues with jsdom execution.

@getodk/scenario:test: [test-node:jsdom      ] TypeError: createRequire is not a function
@getodk/scenario:test: [test-node:jsdom      ]  ❯ ../../node_modules/web-tree-sitter/tree-sitter.js:2045:21
@getodk/scenario:test: [test-node:jsdom      ]  ❯ initializeBinding ../../node_modules/web-tree-sitter/tree-sitter.js:3675:15
@getodk/scenario:test: [test-node:jsdom      ]  ❯ Function.init ../../node_modules/web-tree-sitter/tree-sitter.js:3710:15
@getodk/scenario:test: [test-node:jsdom      ]  ❯ Function.init ../xpath/src/static/grammar/TreeSitterXPathParser.ts:146:3
@getodk/scenario:test: [test-node:jsdom      ]  ❯ Function.init ../xpath/src/static/grammar/ExpressionParser.ts:77:22
@getodk/scenario:test: [test-node:jsdom      ]  ❯ ../xpath/src/expressionParser.ts:23:33

The offending code (I think) is...

    if (ENVIRONMENT_IS_NODE) {
      const { createRequire } = await import("module");
      var require = createRequire(import.meta.url);
    }

Branch: https://github.com/getodk/web-forms/compare/459-update-tree-sitter

[latin-panda]

@garethbowen What do you think about moving this one to the shelve? It doesn't seem we will resolve it for 1.0.0 or 1.1.0.

[garethbowen]

Sure. I have no reason to think this is necessary for 1.0, just a nice to have.