The new "multiple" operator is similar to "search" except it adds some additional features. It allows multiple evaluations of the same payload item by a rule. This solves a problem brought up in #2656

Now evaluations such as the following are possible:

trigger.body.location.latitude:
  type: multiple
  condition: all2any
  pattern:
    item.value:
      type: "lessthan"
      pattern: 40
    item.value#2:
      type: "greaterthan"
      pattern: 50
trigger.body.location.longitude:
  type: multiple
  condition: all2any
  pattern:
    item.value:
      type: "greaterthan"
      pattern: -90
    item.value#2:
      type: "lessthan"
      pattern: -100

In this example the action for this criteria would occur when the latitude and longitude payload data falls outside the area specified, creating a simple box geo-fence.

There are four different criteria conditions:

• all2all - true if all payload items match all criteria items
• all2any - true if all payload items match any criteria items
• any2any - true if any payload items match any criteria items
• any2all - true if any payload items match all criteria items

When specifying payload data in the rule, the "#" symbol and text after it are ignored. This allows dictionary keys to be unique but refer to the same field. Any text can go after the hash.

Using the four different criteria conditions, inclusive or exclusive ranges for the same field are possible.

See tests for more examples.

The multiple operator could eventually replace the search operator.

Closes #2656