bump anyhow to 1.0.103, linting

Author: adwk67

Cargo.lock

@@ -12,7 +12,7 @@ repository = "https://github.com/stackabletech/kafka-operator"
 [workspace.dependencies]
 stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.112.0", features = ["crds", "webhook"] }
 
-anyhow = "1.0"
+anyhow = "1.0.103"
 built = { version = "0.8", features = ["chrono", "git2"] }
 clap = "4.6"
 const_format = "0.2"

Cargo.toml

@@ -28,7 +28,7 @@ pub enum Error {
 }
 
 /// Build a discovery [`ConfigMap`] containing information about how to connect to a certain
-/// [`v1alpha1::KafkaCluster`].
+/// `v1alpha1::KafkaCluster`.
 pub fn build_discovery_configmap(
     validated_cluster: &ValidatedCluster,
     listeners: &[listener::v1alpha1::Listener],

rust/operator-binary/src/controller/build/resource/discovery.rs

@@ -1,6 +1,6 @@
 //! Builds the cluster-wide RBAC resources (`ServiceAccount` and `RoleBinding`).
 //!
-//! The names come from [`ResourceNames`](stackable_operator::v2::role_utils::ResourceNames)
+//! The names come from [`ResourceNames`]
 //! and are identical to the previously used `commons::rbac::build_rbac_resources`
 //! (`<cluster>-serviceaccount`, `<cluster>-rolebinding`, `<product>-clusterrole`), so switching to
 //! this builder does not rename any RBAC objects.

rust/operator-binary/src/controller/build/resource/rbac.rs

@@ -790,7 +790,7 @@ fn add_common_pod_config(
 ///
 /// Whether Vector is enabled, the per-container log config and the (validated) aggregator
 /// discovery `ConfigMap` name are resolved up-front in
-/// [`ValidatedLogging`](crate::controller::validate::ValidatedLogging). The container mounts the
+/// [`ValidatedLogging`]. The container mounts the
 /// static `vector.yaml` from the `config` volume and is driven by the env vars the
 /// [`vector_container`] sets.
 fn add_vector_container(