fix: improve translation error detection

[mehalter]

This improves the error detection by not necessarily requiring the number of matches to equal the number of parameters. This happens when the number of parameters are 0 but there is a quoted string in the message. It should only error if it is unable to retrieve a specific match.

This also has some performance stuff by doing less if there are no errors or parameters

[mehalter]

here is an example of an error code that didn't work because it has no parameters but does have 'const' in the diagnostic text

[dmmulroy]

Lgtm - @mehalter thank you again for jumping into this project! Any shot I could buy you a coffee somehow?

I'd also note that I'm working on rewriting and trying to more closely match the parseEngine from Matt Pococks TS implementation for VS - in fact I found a bug in the original this morning while working through it :) (mattpocock/ts-error-translator#268 (comment))

I wrote the internals of this quite a few months ago to support some other work and deviated from the way his worked to support those goals, so working on getting back to the baseline now

[mehalter]

Nah for reals, no worries at all! I'm glad to help out! I am the maintainer of AstroNvim and the users over on our discord have been excited about your plugin and getting it into the AstroNvim ecosystem!