Feature/match path pattern expression

[Shylock-Hg]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Close #3131

Description:

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 .....

[Sophie-Xie]

What incompatibility does it cause? In same X(x.y.z) version, release should remain compatible. Any client release should use with any core release, if X is same.

[Shylock-Hg]

What incompatibility does it cause? In same X(x.y.z) version, release should remain compatible. Any client release should use with any core release, if X is same.

See this case,

nebula/tests/tck/features/match/Base.feature

Line 713 in 61de3d2

# Parser will treat '(v)' as match node instead label expression, so

Now don't support return (v)

[Shylock-Hg]

Replaced by #3997