fix: query param matching handles params that are not in same order

[birme]

This PR addresses #45 and fix an issue where query param matching required the params to be in the same order. This is solved by parsing the query param string and sort the params before string comparison.

In addition this PR includes:

Validate types for match in catu claim is according to spec:

match = {
  ? exact-match ^ => tstr,
  ? prefix-match ^ => tstr,
  ? suffix-match ^ => tstr,
  ? contains-match ^ => tstr,
  ? regex-match ^ => [ tstr, * tstr ],
  ? sha256-match ^ => bstr,
  ? sha512-256-match ^ => bstr
}

And also adds the useRecords=false option to CBOR encoder/decoder