Consider dropping the support of uint64/int64 data type for some operators

[lisa0314]

As @RafaelCintron mentioned in Chromium CL-5470845 for triangular,

Web developers are not going to test on every Windows combinations for these surprise failures that aren't documented anywhere. If this cannot be supported reliably, we should spec the operator to not support these data types from the jump.

Currently, public OS release was DML FL 4.0 on Windows 11 22H1, some operators and operand data type can't be supported reliably. Maybe we should spec these operators to not support these data types, such as int64/uint64.

[lisa0314]

The operators listed below can't support uint64/int64 before DML FL4.1:

• Expand: implemented by DML_ELEMENT_WISE_IDENTITY_OPERATOR.
• Slice: implemented by DML_SLICE_OPERATOR
• Triangular: implemented by decompose with DML_ELEMENT_WISE_BIT_AND_OPERATOR and DML_SLICE_OPERATOR, DML_ELEMENT_WISE_IDENTITY_OPERATOR
• Gather: implemented by DML_GETHER_OPERATOR
• Transpose: implemented by DML_ELEMENT_WISE_IDENTITY_OPERATOR

[a-sully]

Related to #653. Note that CoreML does not natively support 64-bit types at all. If WebNN specifies that an operator uses 64-bit types, then either the operator will not be supported on Mac, or the user agent must emulate it outside of CoreML

[inexorabletash]

For DML at least, aren't we expecting that most browsers would include their own copy of the library rather than relying on whatever happens to be on the system? That would remove the need to consider older DML versions when considering data type / operator support.