Pact Foundation

FFI call:

``````
pactffi_with_query_parameter_v2($interactionId, 'pages', 0, '{"value":"1","regex":"\\d+","pact:matcher:type":"regex"}');
``````


Http client query:

```?pages=2&amp;pages=3```

Trimmed logs about matching rule:

```2023-10-23T01:46:59.767978Z DEBUG tokio-runtime-worker pact_matching:      matching_rules: MatchingRules { rules: {QUERY: MatchingRuleCategory { name: QUERY, rules: {DocPath { path_tokens: [Root, Field("pages"), Index(0)], expr: "$.pages[0]" }: RuleList { rules: [Regex("\\d+")], rule_logic: And, cascaded: false }} }} }```

Logs about mismatches:

```2023-10-23T01:46:59.768473Z DEBUG tokio-runtime-worker pact_matching: --&gt; Mismatches: [QueryMismatch { parameter: "pages", expected: "", actual: "3", mismatch: "Expected query parameter 'pages' with value '' but was '3'" }, QueryMismatch { parameter: "pages", expected: "[\"1\"]", actual: "[\"2\", \"3\"]", mismatch: "Expected query parameter 'pages' with 1 value(s) but received 2 value(s)" }]```

Note: I expect *every values* of `pages` are integer, *not* the *first* value.

But I think there are no way to make `pactffi_with_query_parameter_v2` ignore the index `0` ,just like how `pactffi_with_header_v2` did:

&gt; NOTE: If you pass in a form with multiple values, the index will be ignored.

This is the problem `expr: "$.pages[0]"`, there is no way with the FFI params to specify `*` instead of 0

How about updating `pactffi_with_query_parameter_v2` to allow something like this (change value from string to array):
```pactffi_with_query_parameter_v2($interactionId, 'pages', 0, '{"value":["1", "2", ["3"]],"regex":"\\d+","pact:matcher:type":"regex"}');```
then it ignore the  index `0`

Here is the ticket <https://github.com/pact-foundation/pact-reference/issues/332>