[PATCH proxmox-yew-comp] fix #7963: acme: filter ACME DNS Plugins by their human-readable name

[Lukas Wagner <l.wagner@proxmox.com>]

In the picker, we only show the human-readable plugin name. For some
plugins, this name differs from the actual plugin id (example:
"Cloudflare Managed DNS" has id "cf"), which makes filtering behavior
unexpected for users.

Fixed by setting a custom filter function for the underlying GridPicker.

The filter function uses `contains` instead of `starts_with`, as doing
so makes it easier to find certain plugins where human-readable name
does not start with most commonly used term for the service. For
instance, some users might type `aws` or `route 53` to find the
`Amazon Route 53 (AWS)` plugin.

Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
 src/acme/acme_challenge_selector.rs | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/acme/acme_challenge_selector.rs b/src/acme/acme_challenge_selector.rs
index 34fd3ee..0b52b49 100644
--- a/src/acme/acme_challenge_selector.rs
+++ b/src/acme/acme_challenge_selector.rs
@@ -58,6 +58,9 @@ pub struct AcmeChallengeSchemaItem {
     #[serde(rename = "type")]
     pub ty: String,
     pub schema: Value,
+    /// Human-readable name.
+    /// The backend sets this to the same value as `id` if no `name` is defined the schema.
+    pub name: String,
 }
 
 impl ExtractPrimaryKey for AcmeChallengeSchemaItem {
@@ -108,6 +111,12 @@ impl Component for ProxmoxAcmeChallengeSelector {
                     .class("pwt-flex-fit");
 
                 GridPicker::new(table)
+                    .filter(|plugin: &AcmeChallengeSchemaItem, query: &str| {
+                        let name = plugin.name.to_ascii_uppercase();
+                        let query = query.to_ascii_uppercase();
+
+                        name.contains(&query)
+                    })
                     .selection(args.selection.clone())
                     .on_select(args.controller.on_select_callback())
                     .into()
-- 
2.47.3