Fix wrong properties prune in length function.

[Shylock-Hg]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Close #4862

Description:

length function also could accept STRING input but not only PATH. So for compatibility, I disable this optimization. It lead to performance regression when return length(p) only.

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

[jievince]

Could we check if the argument type is path？

[Shylock-Hg]

Could do it in later optimization. This PR just fix bug.

[jievince]

I remember It was to optimze length(path) related query in ldbc. @nevermore3

[nevermore3]

yes, we can add the type of the variable to the operator later, which can be more precise when clipping attributes

[codesigner]

LGTM