Optimizer: add test cases for predicate simplifications

[ghazalfamilyusa]

Issue Number: ref #40221

Problem Summary:
This PR just adds tests of various predicate simplification optimizations cases. The purpose of the test is to
(1) document existing cases. This include (a) removing redundancy for identical simple predicates
like =, <>, > and <, >= and <=, (b) un-satisfiable conditions like x=1 and x <> 1 (c) intersection of two in lists.
(2) list cases not working currently and should be addressed in future optimizations. These cases cover
the use case in #40221) and more like intersection of two "not in" lists.
(3) establish a place holder for predicate simplification is a general optimizer rewrite rule and sub-rules.

Tests

• [] Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• fixdb
• hawkingrei

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[sre-bot]

All committers have signed the CLA.

[fixdb]

Please sign the CLA and remove the unintentional change, other than that, looks good to me!

[ghazalfamilyusa]

Please sign the CLA and remove the unintentional change, other than that, looks good to me!

Removed the unintentional change. For CLA, I signed it yesterday and still showing it is pending. To make sure, I added my ping cap email [email protected] to my github account.

[fixdb]

+1
LGTM. We may need help from IT about the CLA.

[ghazalfamilyusa]

Hi, I have done that many time so far. I get that I already signed it and somehow it is not clearing in the PR. See image of what I keep getting showing that I already accepted.

…

On Jan 26, 2023, at 8:36 PM, Weizhen Wang ***@***.***> wrote: @ghazalfamilyusa <https://github.com/ghazalfamilyusa> Please sign the CLA. — Reply to this email directly, view it on GitHub <#40775 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3EVQBJQQZAOXIH2HMBHPS3WUNGFNANCNFSM6AAAAAAUG2EF2Y>. You are receiving this because you were mentioned.

[Reminiscent]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 127ad80c2739ec9fab649907cdeda8310b3d492b

[ti-chi-bot]

@ghazalfamilyusa: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[hawkingrei]

/hold Please resolve the CLA problem.

[ti-chi-bot]

Merge canceled because a new commit is pushed.

[ghazalfamilyusa]

Process got complicated when a different email is used for the commit. Will do another clean PR.