clippy: fix

Instead of applying the fixes, it is better to ignore the lints.
In once case, we have false positives. In the other case, we actually
like the old style. For instance:

We prefer

```
/// # Parameters
/// * `some_param` This parameter has a
///    very long description
```

over

```
/// # Parameters
/// * `some_param` This parameter has a
/// very long description
```

Author: phip1611

uefi-raw/src/lib.rs

@@ -21,6 +21,7 @@
     missing_debug_implementations,
     unused
 )]
+#![allow(clippy::doc_overindented_list_items)]
 
 #[macro_use]
 mod enums;

uefi/src/lib.rs

@@ -227,6 +227,7 @@
     unsafe_op_in_unsafe_fn,
     unused
 )]
+#![allow(clippy::doc_overindented_list_items)]
 
 #[cfg(feature = "alloc")]
 extern crate alloc;

uefi/src/proto/driver/component_name.rs

@@ -184,6 +184,7 @@ impl ComponentName {
     ///
     /// [ISO 639-2]: https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes
     /// [RFC 4646]: https://www.rfc-editor.org/rfc/rfc4646
+    #[allow(clippy::missing_const_for_fn)] // false-positive since Rust 1.86
     pub fn supported_languages(&self) -> core::result::Result<LanguageIter, LanguageError> {
         match self {
             Self::V1(cn1) => cn1.supported_languages(),

uefi/src/runtime.rs

@@ -884,6 +884,7 @@ pub struct VariableKey {
 impl VariableKey {
     /// Name of the variable.
     #[deprecated = "Use the VariableKey.name field instead"]
+    #[allow(clippy::missing_const_for_fn)] // false-positive since Rust 1.86
     pub fn name(&self) -> core::result::Result<&CStr16, crate::data_types::FromSliceWithNulError> {
         Ok(&self.name)
     }