Fix Non-determinstic Test SchemaFetchScanOperatorTest#testSchemaFetch…

[mohitbadve]

Description

The test org.apache.iotdb.db.queryengine.execution.operator.schema.SchemaFetchScanOperatorTest#testSchemaFetchResult fails under NonDex tool which detects non-deterministic nature of tests with when non-deterministic data structures are used. The failure here is observed because the results we get from ClusterSchemaTree are not always in determinstic order.

How to Reproduce

mvn -pl iotdb-core/datanode edu.illinois:nondex-maven-plugin:2.1.7:nondex 
-Dtest=SchemaFetchScanOperatorTest#testSchemaFetchResult
-DnondexRuns=10

Error

[ERROR] org.apache.iotdb.db.queryengine.execution.operator.schema.SchemaFetchScanOperatorTest.testSchemaFetchResult -- Time elapsed: 1.146 s <<< FAILURE!
java.lang.AssertionError: expected:<[root.sg.d1.s2, root.sg.d2.a.s2, root.sg.d2.s2]> but was:<[root.sg.d2.s2, root.sg.d2.a.s2, root.sg.d1.s2]>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:120)
	at org.junit.Assert.assertEquals(Assert.java:146)
	at org.apache.iotdb.db.queryengine.execution.operator.schema.SchemaFetchScanOperatorTest.testSchemaFetchResult(SchemaFetchScanOperatorTest.java:100)...

Proposed Solution

Instead of asserting the lists directly, assert the lists without considering the order.
Please let me know if you have any questions or need any additional justification/changes from my side.

---

This PR has:

• been self-reviewed.
  • concurrent read
  • concurrent write
  • concurrent read and write
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods.
• added or updated version, license, or notice information
• added comments explaining the "why" and the intent of the code wherever would not be obvious
  for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold
  for code coverage.
• added integration tests.
• been tested in a test IoTDB cluster.

---

Key changed/added classes (or packages if there are too many classes) in this PR