chore: disallow async locks (RwLock) (#2144)

Author: rumenov

clippy.toml

@@ -12,5 +12,6 @@ disallowed-methods = [
     { path = "crossbeam_channel::unbounded", reason = "Using an unbounded channel most likely will read to unbounded memory growth. Please use a bounded channel instead. If you are intentionally using unbounded channel, use `#[allow(clippy::disallowed_methods)]` to locally disable this check." },
 ]
 disallowed-types = [
-    { path = "tokio::sync::Mutex", reason = "You should only use an asynchronous lock if you need to .await something while the lock is locked. Usually, this is not necessary, and you should avoid using an asynchronous lock when you can. Asynchronous locks are a lot slower than blocking locks. Please read how to share state effectively across async tasks https://tokio.rs/tokio/tutorial/shared-state. If you are intentionally using an async mutex, use `#[allow(clippy::disallowed_types)]` to locally disable this check." },
+    { path = "tokio::sync::Mutex", reason = "You should only use an asynchronous lock if you need to .await something while the lock is locked. Usually, this is not necessary, and you should avoid using an asynchronous lock when you can. Asynchronous locks are a lot slower than blocking locks. Please read how to share state effectively across async tasks https://tokio.rs/tokio/tutorial/shared-state. If you are intentionally using an async Mutex, use `#[allow(clippy::disallowed_types)]` to locally disable this check." },
+    { path = "tokio::sync::RwLock", reason = "You should only use an asynchronous lock if you need to .await something while the lock is locked. Usually, this is not necessary, and you should avoid using an asynchronous lock when you can. Asynchronous locks are a lot slower than blocking locks. Please read how to share state effectively across async tasks https://tokio.rs/tokio/tutorial/shared-state. If you are intentionally using an async RwLock, use `#[allow(clippy::disallowed_types)]` to locally disable this check." },
 ]

rs/boundary_node/ic_boundary/src/core.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use std::{
     error::Error as StdError,
     net::{Ipv6Addr, SocketAddr},

rs/boundary_node/ic_boundary/src/metrics.rs

@@ -1,3 +1,5 @@
+#![allow(clippy::disallowed_types)]
+
 use std::{sync::Arc, time::Instant};
 
 use anyhow::Error;

rs/monitoring/metrics/src/adapter_metrics_registry.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::buckets::{add_bucket, decimal_buckets};
 use futures::future::join_all;
 use futures::future::FutureExt;

rs/orchestrator/src/dashboard.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::{
     catch_up_package_provider::CatchUpPackageProvider, process_manager::ProcessManager,
     registry_helper::RegistryHelper, ssh_access_manager::SshAccessParameters,

rs/orchestrator/src/firewall.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::{
     catch_up_package_provider::CatchUpPackageProvider,
     error::{OrchestratorError, OrchestratorResult},

rs/orchestrator/src/ipv4_network.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::{
     error::{OrchestratorError, OrchestratorResult},
     metrics::OrchestratorMetrics,

rs/orchestrator/src/orchestrator.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::{
     args::OrchestratorArgs,
     boundary_node::BoundaryNodeManager,

rs/orchestrator/src/ssh_access_manager.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use crate::{
     error::{OrchestratorError, OrchestratorResult},
     metrics::OrchestratorMetrics,

rs/pocket_ic_server/src/main.rs

@@ -1,3 +1,4 @@
+#![allow(clippy::disallowed_types)]
 use aide::{
     axum::{
         routing::{get, post},