Update for clippy 1.83 (#441)

* Update for clippy 1.83

Signed-off-by: Michael X. Grey <greyxmike@gmail.com>

* Update clippy for cfg(test) as well

Signed-off-by: Michael X. Grey <greyxmike@gmail.com>

* Exclude dependencies from clippy test

Signed-off-by: Michael X. Grey <greyxmike@gmail.com>

* Fix clippy for rosidl_runtime_rs

Signed-off-by: Michael X. Grey <greyxmike@gmail.com>

---------

Signed-off-by: Michael X. Grey <greyxmike@gmail.com>

Author: mxgrey

rosidl_runtime_rs/src/string/serde.rs

@@ -13,7 +13,7 @@ use super::{
 struct StringVisitor;
 struct WStringVisitor;
 
-impl<'de> Visitor<'de> for StringVisitor {
+impl Visitor<'_> for StringVisitor {
     type Value = String;
 
     fn expecting(&self, formatter: &mut fmt::Formatter) -> fmt::Result {

rosidl_runtime_rs/src/traits.rs

@@ -124,10 +124,11 @@ pub trait RmwMessage: Clone + Debug + Default + Send + Sync + Message {
 ///
 /// Memory ownership by C is achieved by calling `init()` when any string or sequence is created,
 /// as well as in the `Default` impl for messages.
+///
 /// User code can still create messages explicitly, which will not call `init()`, but this is not a
-///  problem, since nothing is allocated this way.
+/// problem, since nothing is allocated this way.
+///
 /// The `Drop` impl for any sequence or string will call `fini()`.
-
 pub trait Message: Clone + Debug + Default + 'static + Send + Sync {
     /// The corresponding RMW-native message type.
     type RmwMsg: RmwMessage;