release-21.2: opt: don't panic on negated geospatial comparison operator

[blathers-crl]

Backport 1/1 commits from #84524 on behalf of @DrewKimball.

/cc @cockroachdb/release

---

Previously, the NegateComparison rule could match geospatial
comparison operators like ~. This would lead to a panic when the
rule attempted to construct the negated version of the expression,
since there is no negation for ~ and other geospatial comparisons.

This patch modifies NegateComparison to directly check
opt.NegateOpMap to ensure that a comparison can be negated before
matching the expression.

Fixes #84476

Release note (bug fix): Fixed a bug introduced in 20.2 that could
cause a panic when an expression contained a geospatial comparison
like ~ that was negated.

---

Release justification:

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is 

[rytaft]

Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @DrewKimball)

[DrewKimball]

TFTR!