[STAL-1960] Add bridge for (TsSymbol <> Name) mappings

[jasonforal]

What problem are you trying to solve?

One of the fundamental design constraints for ddsa was to represent everything that needed to be passed between Rust and JavaScript with a v8 "smi" (a uint31 on 64 bit platforms). At the same time, we want ergonomic APIs that aren't constrained by performance optimizations like this.

Each tree-sitter CST node (that we care about) has a string name (that it internally calls a TSSymbol) to represent its type:

const myNumber = 123;

The node type names for the nodes in this expression are:

const myNumber = 123;     "lexical_declaration"
myNumber = 123            "variable_declarator"
myNumber                  "identifier"
123                       "number"

We want users to be able to author JavaScript rules that can filter nodes by a string name, like "identifier". We also want to be able to let JavaScript rules request nodes of a given type as well.

In pseudo-code:

const nodes = ddsa.getChildren(targetNode, "variable_declarator");

What is your solution?

In the above example (const nodes = ddsa.getChildren(node, "variable_declarator");), this is a function that will make a call to Rust to request additional tree-sitter nodes. Under the hood, we want to be able to translate this to something like:

const nodes = op_get_children(32 /* nodeId (smi) */, 149 /* TSSymbolId (smi) */);

To achieve this, we create and pre-calculate a v8 map with data for each tree-sitter Language. For example, in JavaScript pseudo-code, this would be like:

const symbolMap = new Map([
    [1, "identifier"],
    ["identifier, 1],
    // ...
    [146, "expression_statement"],
    ["expression_statement", 146],
    // ...
    [225, "decorator"],
    ["decorator", 225],
    // ...
]);

With this map, we can always internally represent the type as a numeric id, but use string names in the user-facing JavaScript API.

This map will be exposed on the JavaScript globalThis on a per-language basis so that ddsa will have access to this map.

Alternatives considered

What the reviewer should know

• This is just the bridge implementation -- this code is not live. It will be activated when we switch over to ddsa.

[jasonforal]

Original PR had #385 as the base, so now there are merge conflicts.

Fixing and then to main we go