Implement Ranged on more structs (#6639)

## Summary

I noticed some inconsistencies around uses of `.range.start()`, structs
that have a `TextRange` field but don't implement `Ranged`, etc.

## Test Plan

`cargo test`

crates/ruff_python_semantic/src/binding.rs

@@ -283,6 +283,12 @@ bitflags! {
     }
 }
 
+impl Ranged for Binding<'_> {
+    fn range(&self) -> TextRange {
+        self.range
+    }
+}
+
 /// ID uniquely identifying a [Binding] in a program.
 ///
 /// Using a `u32` to identify [Binding]s should is sufficient because Ruff only supports documents with a

crates/ruff_python_semantic/src/reference.rs

@@ -3,6 +3,7 @@ use ruff_text_size::TextRange;
 use std::ops::Deref;
 
 use ruff_index::{newtype_index, IndexSlice, IndexVec};
+use ruff_python_ast::Ranged;
 use ruff_source_file::Locator;
 
 use crate::context::ExecutionContext;
@@ -26,11 +27,6 @@ impl ResolvedReference {
         self.scope_id
     }
 
-    /// The range of the reference in the source code.
-    pub const fn range(&self) -> TextRange {
-        self.range
-    }
-
     /// The [`ExecutionContext`] of the reference.
     pub const fn context(&self) -> ExecutionContext {
         if self.flags.intersects(SemanticModelFlags::TYPING_CONTEXT) {
@@ -41,6 +37,13 @@ impl ResolvedReference {
     }
 }
 
+impl Ranged for ResolvedReference {
+    /// The range of the reference in the source code.
+    fn range(&self) -> TextRange {
+        self.range
+    }
+}
+
 /// Id uniquely identifying a read reference in a program.
 #[newtype_index]
 pub struct ResolvedReferenceId;