fix: support object/array-formed condition (#212)

[RexSkz]

This PR handles the following scenario:

• If two tests are string, regex, function, use the previous logic (compare the toString result).
• If they are objects or arrays, flatten them and sort the entries, then do the compare.

The order of arrays in tests should not affect the result, e.g. [/a/, /b/] and [/b/, /a/] are the same test. To handle this, we can replace numbers in flattened keys (the numbers are definitely from arrays). For example, a.1.b will be replaced with a.[].b.

Closes #212

---

To let someone with interests understand it quickly, here is an example:

// Original
[
  { and: [/a/, /b/] },
  /c/,
]
[
  /c/,
  { and: [/b/, /a/] },
]

// After flatten
{
  '0.and.0': /a/,
  '0.and.1': /b/,
  '1': /c/,
}
{
  '0': /c/,
  '1.and.0': /b/,
  '1.and.1': /a/,
}

// After using `Object.entries` and replacing numbers with `[]`
[
  ['[].and.[]', /a/],
  ['[].and.[]', /b/],
  ['[]', /c/],
]
[
  ['[]', /c/],
  ['[].and.[]', /b/],
  ['[].and.[]', /a/],
]

// After the sort
[
  ['[]', /c/],
  ['[].and.[]', /a/],
  ['[].and.[]', /b/],
]
[
  ['[]', /c/],
  ['[].and.[]', /a/],
  ['[].and.[]', /b/],
]

Finally, we just compare each item: use the === for [0], and use the toString for [1].