feat!: use tree-sitter build

[clason]

quick test to compare build times on CI:

• ubuntu: 2:09 vs 1:50
• macos: 1:40 vs 1:20 (locally, 95s vs 85s)
• windows: 3:55 vs 5:09

network/load adds large variance, but the windows improvement is significant (and welcome on CI).

Also, adding or removing scanners is no longer a breaking change.

Also also, look at those diffstats 🤩

Notes on possible (upstream) improvements:

1. Ideally, we could build directly into the target location, obviating the need for the move task, but ts b litters debug symbols in the build directory.
2. We could combine generate and build step if ts b generated if necessary. For our purposes, though, we'd need more control:

• ts b builds from parser.c
• ts b src/grammar.json calls ts g src/grammar.json first
• ts b grammar.js calls ts g first

(and ts b would need to take all flags for ts g as well).