fix(graphQL): Fixing set ordering in batchGet of entities

[jjoyce0510]

In a recent change, we migrated from using the legacy snapshot-based batchGet method to a new batchGetV2. In the process, we introduced a bug that causes the ordering of results from batchGet to be non-deterministically changed.

These changes have not yet been released. This PR fixes the issue.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable)

[github-actions]

Unit Test Results (build & test)

  45 files  ±0    45 suites  ±0   15m 4s ⏱️ + 1m 40s
505 tests +1  449 ✔️ +1  56 💤 ±0  0 ❌ ±0 

Results for commit d9ef28a. ± Comparison against base commit 8b716ad.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Results (metadata ingestion)

       5 files  ±0         5 suites  ±0   37m 1s ⏱️ -53s
   274 tests ±0     274 ✔️ ±0    0 💤 ±0  0 ❌ ±0 
1 261 runs  +2  1 233 ✔️ +8  28 💤  - 6  0 ❌ ±0 

Results for commit d9ef28a. ± Comparison against base commit 8b716ad.

♻️ This comment has been updated with latest results.