fix(treesitter): add opts to iter_captures

[Danielkonge]

This is a minor change which makes iter_captures work more like iter_matches. Since both iter_captures and iter_matches uses vim._create_ts_querycursor in a similar way, I don't see why iter_captures wouldn't also allow the opts table. In particular, match_limit also affects iter_captures, and this change would basically fix #26325.

As a side note: While editing the iter_captures code, I noticed that iter_matches doesn't use memoize like iter_captures, is this on purpose? I don't really see the reason for this distinction?

[lewis6991]

As a side note: While editing the iter_captures code, I noticed that iter_matches doesn't use memoize like iter_captures, is this on purpose? I don't really see the reason for this distinction?

iter_captures can flip between different matches so memoize is used to avoid recalculating whether or not the predicates passed. This isn't needed for iter_matches since you will only process a match once.

[Danielkonge]

iter_captures can flip between different matches so memoize is used to avoid recalculating whether or not the predicates passed. This isn't needed for iter_matches since you will only process a match once.

Ah, that makes sense then.

Also, I was considering adding more descriptive types to the opts for both iter_captures and iter_matches, but I have just kept the layout like iter_matches for now.

Wouldn't it be better with something like opts? { max_start_depth?: integer, match_limit?: integer}? Or maybe a named type (though for now there is a difference between iter_captures and iter_matches, since all is not relevant to iter_captures).