Change `equals()` to ignore order based on OGC

[tonystone]

The OGC standard states for Collection types

By the nature of digital representations, collections are inherently ordered by the underlying storage mechanism. Two collections whose difference is only this order are spatially equal and will return equivalent results in any geometric-defined operations.

-- OGC Simple Feature Access - Part 1: Common Architecture v1.2.1 (6.1.3.2)

We currently require specific ordering on our equals() and == since it is based on equals(). The new implementation should possibly be based on the relate method which should ignore ordering.