Eliminate vid predication Filter.

[Shylock-Hg]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Sub job of #4122

Description:

GetVertices will retrieve Vertex by Id set directly, so we don't filter them again in Filter operator, so we eliminate this Filter operator.

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

[nevermore3]

if the vertexIDSeek statement is mixed with other property filtering statements, can we delete the vertexID condition after selecting the vertexID index?

[Shylock-Hg]

if the vertexIDSeek statement is mixed with other property filtering statements, can we delete the vertexID condition after selecting the vertexID index?

We can, but need to refactor VidExtractVisitor and maybe lead to incompatible, so don't refactor it here.

[CPWstatic]

LGTM. Please remove the debug logs.