Static type checks for Jet::Tensor data

[brownj85]

Context:
Users do not get an error message at compile-time if they create a Tensor with an unsupported data type (i.e. not complex<float> or complex<double>). they will instead get a runtime error when JET_ABORT is called one of the gemm bindings.

Description of the Change:
Adds an is_supported_data_type type trait template to TensorHelpers, in the same vein as std::is_arithmetic, that has a true value if the template parameter is a supported type.

Adds template parameter to disable MultiplyTensorData for unsupported types
Removes JET_ABORT calls from gemm bindings, since they are unreachable.

Adds a static_assert to Jet::Tensor that checks if the templated data type
is supported.

Benefits:
It is now impossible for a user to compile a program using an invalid tensor data type, and there is a clear error message when they attempt to do so.

Possible Drawbacks:
None

Related GitHub Issues:

[github-actions]

Test Report (Ubuntu)

    1 files  ±0      1 suites  ±0   0s ⏱️ ±0s
215 tests ±0  215 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
483 runs  ±0  483 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit b9eeabc. ± Comparison against base commit b9eeabc.

♻️ This comment has been updated with latest results.

[github-actions]

Test Report (MacOS)

    1 files  ±0      1 suites  ±0   0s ⏱️ ±0s
215 tests ±0  215 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
483 runs  ±0  483 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit b9eeabc. ± Comparison against base commit b9eeabc.

♻️ This comment has been updated with latest results.

[Mandrenkov]

Awesome work! It's not too often you can improve performance and developer productivity at the same time.

[mlxd]

Excellent idea!

[Mandrenkov]

Looks good to me!