getTypeInfo's result are not ordered as specified

[onacit]

Driver version

Provide the JDBC driver version (e.g. 10.2.0).

SQL Server version

Provide the output of executing SELECT @@VERSION on your target SQL Server.

Client Operating System

Provide the Operating System the client application is running on.

JAVA/JVM version

Provide the JAVA/JVM version (e.g. java version "1.8.0").

Table schema

Provide the table schema to repro the issue.

Problem description

group is not sorted according to Comparator$$Lambda/0x00000008001601f8 comparator because element 1:
  TypeInfo(super=AbstractMetadataType(super=com.github.jinahya.database.metadata.bind.TypeInfo@30a30f43, unmappedValues={USERTYPE=0, INTERVAL_PRECISION=null}), typeName=time,
    dataType=92, <<<<<<<<<<<<<<<<<<<<<<<<
    precision=16, literalPrefix=', literalSuffix=', createParams=scale, nullable=1, caseSensitive=false, searchable=3, unsignedAttribute=null, fixedPrecScale=false, autoIncrement=null, localTypeName=time, minimumScale=0, maximumScale=7, sqlDataType=null, sqlDatetimeSub=null, numPrecRadix=null)
is not less or equal than element 2:
  TypeInfo(super=AbstractMetadataType(super=com.github.jinahya.database.metadata.bind.TypeInfo@79d469ea, unmappedValues={USERTYPE=0, INTERVAL_PRECISION=null}), typeName=xml,
    dataType=-16, <<<<<<<<<<<<<<<<<<<<<<
precision=0, literalPrefix=N', literalSuffix=', createParams=null, nullable=1, caseSensitive=true, searchable=0, unsignedAttribute=null, fixedPrecScale=false, autoIncrement=null, localTypeName=xml, minimumScale=null, maximumScale=null, sqlDataType=null, sqlDatetimeSub=null, numPrecRadix=null)

Expected behavior

A clear and concise description of what you expected to happen.

Actual behavior

Output of what you actually see.

Error message/stack trace

Complete error message and stack trace.

Any other details that can be helpful

Add any other context about the problem here.

JDBC trace logs

Provide the JDBC driver trace logs. Instructions can be found here: https://docs.microsoft.com/sql/connect/jdbc/tracing-driver-operation

[Jeffery-Wasty]

Related to #2321. Because of the similarity, I will provide updates on both these issues on the #2321 page.

[Jeffery-Wasty]

This will be added to our backlog. Putting aside whether this is possible (still unclear), a change would involve an extra, substantial, performance impact, and we're still not sure what the downstream effect of changing the order from what SQL server gives us is. We'll revisit this during a later triage.