Improve common error messages

[GregoryComer]

🚀 The feature, motivation and pitch

This is a tracking task for improving clarity on common error messages seen by users, based on early adopter experiences and filed issues.

• Tensor size errors
  • Improve error messages for tensor size errors #7453
• Input DType mismatch
  • Log dtype names on input dtype mismatch #7537
• Include EValue tag names in string error messages
• Include error enum strings for top-level errors in common locations (pybinding code, method load, method execute)

Feel free to add any additional error messages that we can improve in the comments.

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @mergennachin @byjlw

[swolchok]

The ET_LOG_AND_RETURN errors in kernels/portable/cpu/util could be systematically improved:

• the ones containing tensors_have_same_size_at_dims should report the shape using the newly added tensor_shape_to_c_string
• all of them should be reporting the relevant values that caused the check to fail; often the text of the check is not maximally helpful for debugging because it contains references to variables, which of course are not printed