Issue with query string parsing in 10.11.2

Software versions

Please provide at least OS and version of pact-js

OS: tested on Linux and Mac
Pact Node version: 10.11.2
Node Version: 12.18.0

FYI just found an issue relating to query string parsing in this version of the standalone. I need to get to the bottom of why, but an example in the JS repo just started failing after upgrade:

Request:

    const catsListRequest = {
      uponReceiving: "a request for cats with given catId",
      withRequest: {
        method: "GET",
        path: "/cats",
        query: {
          "catId[]": Matchers.eachLike("1"),
        },
        headers: {
          Accept: "application/json",
        },
      },
    }

Client code:

exports.getMeCats = endpoint => {
  const url = endpoint.url

  return axios
    .request({
      method: "GET",
      baseURL: url,
      url: "/cats?catId[]=2&catId[]=3",
      headers: { Accept: "application/json" },
    })
    .then(response => response.data)
}

Log file:

E, [2021-01-27T22:38:04.829205 #15023] ERROR -- : No matching interaction found for GET /cats?catId[]=2&catId[]=3
E, [2021-01-27T22:38:04.829228 #15023] ERROR -- : Interaction diffs for that route:
E, [2021-01-27T22:38:04.829675 #15023] ERROR -- : Diff with interaction: "a request for cats with given catId" given "i have a list of cats"
Diff
--------------------------------------
Key: - is expected
     + is actual
Matching keys and values are not shown
 {
   "query": {
-    "catId[]": [
-      "1",
+    "catId": [
+      "2",
+      "3"
     ]
   }
 }
Description of differences
--------------------------------------
* Could not find key "catId[]" (keys present are: catId) at $.query
* Did not expect the key "catId" to exist at $.query
W, [2021-01-27T22:38:04.836258 #15023]  WARN -- : Verifying - actual interactions do not match expected interactions.
Incorrect requests:
	GET /cats?catId[]=2&catId[]=3 (request query did not match)
W, [2021-01-27T22:38:04.836304 #15023]  WARN -- : Incorrect requests:
	GET /cats?catId[]=2&catId[]=3 (request query did not match)

I’ll dig into more later, but this was the quickest spot to re-raise the issue