Argument plan node does not depend on the right start node when explaining the query

[yixinglu]

Please check the FAQ documentation before raising an issue

Describe the bug (required)

when explaining the following query, we'll get the invalidate execution plan:

explain match (a:player) match (a)-[:like]-(b) return b;

The execution plan generated by explain lost the dependencies.

-----+----------------+--------------+----------------+-----------------------------------
|  5 | Argument       |              |                | outputVar: {                     |
|    |                |              |                |   "colNames": [                  |
|    |                |              |                |     "a"                          |
|    |                |              |                |   ],                             |
|    |                |              |                |   "type": "DATASET",             |
|    |                |              |                |   "name": "__Argument_5"         |
|    |                |              |                | }                                |
|    |                |              |                | inputVar: __AppendVertices_3     |
-----+----------------+--------------+----------------+-----------------------------------
|  6 | Start          |              |                | outputVar: {                     |
|    |                |              |                |   "colNames": [],                |
|    |                |              |                |   "name": "__Start_6",           |
|    |                |              |                |   "type": "DATASET"              |
|    |                |              |                | }                                |
-----+----------------+--------------+----------------+-----------------------------------

Your Environments (required)

• OS: uname -a
• Compiler: g++ --version or clang++ --version
• CPU: lscpu
• Commit id (e.g. a3ffc7d8)

How To Reproduce(required)

Steps to reproduce the behavior:

1. Step 1
2. Step 2
3. Step 3

Expected behavior

Additional context