[K9VULN-1925] fix: improve unsound test by testing the production code path

[amaanq]

What problem are you trying to solve?

In #555 we added support for timing out tree-sitter query executions, as this was necessary to prevent the analyzing spinning forever in case a query suffered from combinatorial explosion. However, with that change, the test added to verify this actually works used the shorthand_execute_rule_internal function, when it should have used shorthand_execute_rule instead because the former does not test the production code path, so any changes to JsRuntime::execute_rule that affect the query timeout will not be caught by the test, unless the corresponding internal function is updated as well.

What is your solution?

Instead of using shorthand_execute_rule_internal, we should be using shorthand_execute_rule to test the production code path, which this PR does.

Alternatives considered

What the reviewer should know

shorthand_execute_rule takes in an optional ExecuteOptions struct. All tests that use this function, though, pass in None for this argument, and as such, never suffered from the fact that the fields of this struct are private, and there's no method on this struct to create an instance of it. As such, I've marked the fields as pub(crate) so that I can create this struct with a timeout and pass it into shorthand_execute_rule.