support intersect/minus for cypher

[jievince]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Close #5115,
By the way, fix #5113

Description:

Usage:
cypher_statement1 UNION/INTERSECT/MINUS cypher_statement2
e.g.

match (v:player) where id(v) == "Tony Parker" return v
union/intersect/minus
match (v:player) where id(v) == "Tim Duncan" return v

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

[Shylock-Hg]

Do we need it? As I known, it's not included in Open Cypher specification.

[jievince]

Do we need it? As I known, it's not included in Open Cypher specification.

Union/Intersect/Minus is very useful. And openCypher has a pr to include them, but they forget to merge it.
opencypher/openCypher#227
neo4j/neo4j#2694

[MuYiYong]

good job！These will enrich our match statement capabilities, and it's better to give some examples.

[HarrisChu]

we have a bug before, go + return should be forbidden, e.g.

GO 3 STEP FROM {0} OVER KNOWS yield $$.Person.firstName | return count(*)

this pr would fix the issue, but would make it incompatible if they use go + return...

[HarrisChu]

cc @Sophie-Xie

[abby-cyber]

vesoft-inc/nebula-docs-cn#2499
vesoft-inc/nebula-docs-cn#2542