Add relevant labeled ranges to existing diagnostics in rules

[camchenry]

Now that #651 is merged, we can add labeled ranges to diagnostics. I'd like to audit every rule and try to add some improved error messages and information.

Rules checked

• await_thenable
• consistent_return
• consistent_type_exports - feat: improve consistent-type-exports diagnostics quality #880
• dot_notation
• no_array_delete
• no_base_to_string
• no_confusing_void_expression
• no_deprecated
• no_duplicate_type_constituents
• no_floating_promises - feat(no-floating-promises): improve diagnostics #1093
• no_for_in_array
• no_implied_eval
• no_meaningless_void_operator
• no_misused_promises - feat(no-misused-promises): improve diagnostics #1101
• no_misused_spread
• no_mixed_enums
• no_redundant_type_constituents - feat(no-redundant-type-constituents): add diagnostic labels #1129
• no_unnecessary_boolean_literal_compare
• no_unnecessary_condition - feat(no-unnecessary-condition): improve diagnostics #1092
• no_unnecessary_qualifier
• no_unnecessary_template_expression - This could be improved but honestly hard to say exactly how - going to leave it alone for now, but open to suggestions here
• no_unnecessary_type_arguments - Acceptable as-is I think
• no_unnecessary_type_assertion - feat: improve quality of no-unnecessary-type-assertion diagnostics #693
• no_unnecessary_type_conversion - feat: add labeled ranges to diagnostic for no-unnecessary-type-conversion #678
• no_unnecessary_type_parameters - feat: improve no-unnecessary-type-parameters diagnostic #690
• no_unsafe_argument
• no_unsafe_assignment - feat(no-unsafe-assignment): improve diagnostics #1105
• no_unsafe_call
• no_unsafe_enum_comparison
• no_unsafe_member_access
• no_unsafe_return - feat(no-unsafe-return): improve diagnostics #1110
• no_unsafe_type_assertion - feat(no-unsafe-type-assertion): improve diagnostics #1111
• no_unsafe_unary_minus
• non_nullable_type_assertion_style
• only_throw_error
• prefer_find
• prefer_includes
• prefer_nullish_coalescing
• prefer_optional_chain
• prefer_promise_reject_errors
• prefer_readonly
• prefer_readonly_parameter_types
• prefer_reduce_type_parameter
• prefer_regexp_exec
• prefer_return_this_type
• prefer_string_starts_ends_with
• promise_function_async
• related_getter_setter_pairs
• require_array_sort_compare
• require_await
• restrict_plus_operands - feat: restrict-plus-operands: improve diagnostic #725
• restrict_template_expressions - feat: restrict-template-expressions: move type to labeled range #724
• return_await
• strict_boolean_expressions
• strict_void_return
• switch_exhaustiveness_check
• unbound_method - feat: add labeled range for unbound-method #718
• use_unknown_in_catch_callback_variable

[camc314]

@camchenry it might be nice if we update oxc_miette to support labels in multiple files, this way, for certain rules (i was thinking no-floating-promises), we can show where the diagnostic is (primary span), and a reference to the declaration (ideally showing the type)