Enable collection node for parameter alias

[xuzhg]

Issues

This pull request fixes #1161.

Description

• So far, the parameter alias is designed as SingleValueNode.
• No matter what the real value is.
• For example:
• ~/people?$filter=Id in @p1&@p1=RelatedIds
• Where 'RelatedIds' is a collection property.

This PR is to support this. In this PR:

1. Introduce a new class as "ParameterAliasCollectionNode", which is a parameter alias node but point to a collection value.
2. Keep "ParameterAliasNode" unchanged for single value node
3. Add Test codes to verify the changes.

The reason to change it is that it's time to introduce this breaking change for a public property from
"IDictionary<string, SingleValueNode>" to
"IDictionary<string, QueryNode>".

Checklist (Uncheck if it is not completed)

• Test cases added
• Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

Repository notes

Team members can start a CI build by adding a comment with the text /AzurePipelines run to a PR. A bot may respond indicating that there is no pipeline associated with the pull request. This can be ignored if the build is triggered.

Team members should not trigger a build this way for pull requests coming from forked repositories. They should instead trigger the build manually by setting the "branch" to refs/pull/{prId}/merge where {prId} is the ID of the PR.

[xuzhg]

/AzurePipelines run

[xuzhg]

/AzurePipelines run