Merge vscode-parse-tree into Cursorless and check .wasm files into source control

[pokey]

Still in draft; just capturing some thoughts

Context

The issue motivating this decision, and any context that influences or constrains the decision.

Desiderata

• renovate bot / dependabot should be able to bump versions of tree-sitter grammars and automatically merge them if they pass tests
• developers not needing to change parse tree versions shouldn't need to mess with emscripten
• it should remain easy to clone the cursorless repo
• as little magic as possible
• it should be easy to bump tree-sitter grammar version if you want to
• it should b easy to add a new language

Options considered

Decision

The change that we're proposing or have agreed to implement.

• Add vscode-parse-tree as package in cursorless monorepo
• Track parser versions in devDependencies of this package
• Keep using GItHub sha for package versions
• Check .wasm files into source control, along with manifest file indicating source version, etc
• Add CI step to automatically build wasms if they're out of date. Potentially have it include signature in manifest so that can only be built in CI to mitigate security risks of binary blobs that can't be code reviewed

If performance becomes an issue with all the .wasm files in source control, we can advise cloning cursorless as follows:

git clone --filter=blob:limit=50k [email protected]:cursorless-dev/cursorless.git

See https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/ for more info

Consequences

What becomes easier or more difficult to do and any risks introduced by the change that will need to be mitigated.