Fix non deterministic test - RoleTest#testRole_InitAndSerialize

[mohitbadve]

Description

The test org.apache.iotdb.db.auth.entity.RoleTest#testRole_InitAndSerialize fails under NonDex tool which detects non-deterministic nature of tests with when non-deterministic data structures are used. The failure behavior is defined by non-deterministic ordering of pathPrivilegeList and systemPrivilegeSet.

How to Reproduce

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

Error

[INFO] Running org.apache.iotdb.db.auth.entity.RoleTest
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.312 s <<< FAILURE! -- in org.apache.iotdb.db.auth.entity.RoleTest
[ERROR] org.apache.iotdb.db.auth.entity.RoleTest.testRole_InitAndSerialize -- Time elapsed: 0.267 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<...legeList=[root.ln : [WRITE_DATA READ_SCHEMA_with_grant_option]], systemPrivilegeSe...> but was:<...legeList=[root.ln : [READ_SCHEMA_with_grant_option WRITE_DATA]], systemPrivilegeSe...>
	at org.junit.Assert.assertEquals(Assert.java:117)
	at org.junit.Assert.assertEquals(Assert.java:146)
	at org.apache.iotdb.db.auth.entity.RoleTest.testRole_InitAndSerialize(RoleTest.java:48) ...

Proposed Solution

Assert the role.toString by handling the above catch. Extract and assert the list and set instead of asserting string directly.
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