chore: upgrade to Rust 1.80.0

crates/biome_analyze/src/registry.rs

@@ -95,7 +95,7 @@ impl<L: Language> RegistryVisitor<L> for MetadataRegistry {
 /// we have:
 /// - Syntax Phase: No services are offered, thus its rules can be run immediately;
 /// - Semantic Phase: Offers the semantic model, thus these rules can only run
-/// after the "SemanticModel" is ready, which demands a whole transverse of the parsed tree.
+///     after the "SemanticModel" is ready, which demands a whole transverse of the parsed tree.
 pub struct RuleRegistry<L: Language> {
     /// Holds a collection of rules for each phase.
     phase_rules: [PhaseRules<L>; 2],

crates/biome_cli/src/service/mod.rs

@@ -72,11 +72,11 @@ type JsonRpcResult = Result<Box<RawValue>, TransportError>;
 /// This structs holds an instance of the `tokio` runtime, as well as the
 /// following fields:
 /// - `write_send` is a sender handle to the "write channel", an MPSC channel
-/// that's used to queue up requests to be sent to the server (for simplicity
-/// the requests are pushed to the channel as serialized byte buffers)
+///     that's used to queue up requests to be sent to the server (for simplicity
+///     the requests are pushed to the channel as serialized byte buffers)
 /// - `pending_requests` is handle to a shared hashmap where the keys are `u64`
-/// corresponding to request IDs, and the values are sender handles to oneshot
-/// channel instances that can be consumed to fulfill the associated request
+///     corresponding to request IDs, and the values are sender handles to oneshot
+///     channel instances that can be consumed to fulfill the associated request
 ///
 /// Creating a new `SocketTransport` instance requires providing a `tokio`
 /// runtime instance as well as the "read half" and "write half" of the socket
@@ -87,12 +87,12 @@ type JsonRpcResult = Result<Box<RawValue>, TransportError>;
 ///
 /// This concurrent handling of I/O is implemented useing two "background tasks":
 /// - the `write_task` pulls outgoing messages from the "write channel" and
-/// writes them to the "write half" of the socket
+///     writes them to the "write half" of the socket
 /// - the `read_task` reads incoming messages from the "read half" of the
 /// - the `read_task` reads incoming messages from the "read half" of the
-/// socket, then looks up a request with an ID corresponding to the received
-/// message in the "pending requests" map. If a pending request is found, it's
-/// fulfilled with the content of the message that was just received
+///   socket, then looks up a request with an ID corresponding to the received
+///   message in the "pending requests" map. If a pending request is found, it's
+///   fulfilled with the content of the message that was just received
 ///
 /// In addition to these, a new "foreground task" is created for each request.
 /// Each foreground task creates a oneshot channel and stores it in the pending