Handle PortToConnect correctly, when same node recommendations are returned from ML API

[reddyashish]

Purpose

https://jira.autodesk.com/browse/DYN-5645

Now the correct port is connected when same node recommendations are returned from ML API. The results are displayed as list box and not as menu items. So we won't be able to provide sub menu functionality.

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated
• This PR contains no files larger than 50 MB

Release Notes

Handle PortToConnect correctly, when same node recommendations are returned from ML API

Reviewers

@QilongTang

FYIs

@DynamoDS/dynamo

[QilongTang]

Hi @reddyashish Is this PR just for the bug that clicking on each entry will connect to the right port instead? you mentioned that we cant implement the UI changes for sub menu items correct?

[reddyashish]

Yes, just for that bug.

[reddyashish]

Yes, just for that bug.

[reddyashish]

@QilongTang Only 1 flaky test now InsideCustomNode_NotPlacedInHomeWorkspace_NoGeometry.

[QilongTang]

@reddyashish And we are still not sure which PR caused that flaky test right? Are you fine with Morpheus team merging PRs with new flaky tests? @mjkkirschner @sm6srw or would you rather us investigate this a bit more?

[reddyashish]

Yeah not sure yet. Lets see the results from Mike's PR #13900, if any test fails