Increase performance for Tree sitter matches

[AndreasArvidsson]

First, were checking the captures against the SCM files in production, which was an oversight - should only be happening in debugging.

Secondarily, the existing implementation multiple map and filters. This part of the code is very time sensitive and can run quite long for large files since we are iterating every capture in the entire file.

This implementation aims to reduce iteration steps

Fixes #2656

Checklist

• [/] I have added tests
• [/] I have updated the docs and cheatsheet
• [/] I have not broken the cheatsheet

[phillco]

We're going to test the performance of the test change and the captured to for loop rewrite separately so we can get a better sense for where the improvement is. The loop rewrite is still a nice code cleanliness change on its own, but we'd like to know how much more efficient it is to better calibrate JavaScript performance mentally.

[AndreasArvidsson]

Now I have some data

529k lines json, 11 iterations, median value

• main, checking captures: 4201ms
• main, don't check captures: 3944ms
• pr, checking captures: 3878ms
• pr, don't check captures: 3754ms

[phillco]

Total performance improvement: 11.45%

• Not checking captures: 8.3%
• Loop rewriting: 3.2%