fix(sqlparser): align operator precedence with PostgreSQL

[xiangjinwu]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Follow the operator precedence specified by PostgreSQL:
https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-PRECEDENCE

• No more magic number for precedence.
• Some operators in upstream are for non-PG dialects or old PG version, they are not removed to keep this PR focused and short: xor, ==, <=>, !
• See test cases for operations / expressions affected.

Fixes #8140
Related: #7665

Checklist For Contributors

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

• My PR DOES NOT contain user-facing changes.

[codecov]

Codecov Report

Merging #8174 (0e05fe6) into main (7f237d7) will decrease coverage by 0.01%.
The diff coverage is 98.00%.

@@            Coverage Diff             @@
##             main    #8174      +/-   ##
==========================================
- Coverage   71.85%   71.84%   -0.01%     
==========================================
  Files        1129     1129              
  Lines      181263   181272       +9     
==========================================
+ Hits       130239   130241       +2     
- Misses      51024    51031       +7     

Flag	Coverage Δ
rust	71.84% <98.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/sqlparser/src/parser.rs	91.52% <98.00%> (+0.06%)	⬆️
...torage/src/hummock/local_version/pinned_version.rs	88.75% <0.00%> (-0.63%)	⬇️
src/meta/src/hummock/mock_hummock_meta_client.rs	65.46% <0.00%> (-0.52%)	⬇️
src/object_store/src/object/mod.rs	48.45% <0.00%> (-0.42%)	⬇️
src/object_store/src/object/mem.rs	86.87% <0.00%> (-0.39%)	⬇️
src/storage/src/hummock/sstable_store.rs	64.62% <0.00%> (-0.32%)	⬇️
src/common/src/cache.rs	97.15% <0.00%> (-0.11%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[xxchan]

nice work 🤯

[mergify]

Hey @xiangjinwu, this pull request failed to merge and has been dequeued from the merge train. If you believe your PR failed in the merge train because of a flaky test, requeue it by clicking "Update branch" or pushing an empty commit with git commit --allow-empty -m "rerun" && git push.

[kwannoel]

This approach is much more clear 👍 thanks for this!