fix(cleanuparr): drop webui, which the add-on linter rejects under ingress

`frenck/action-addon-linter` fails the build with "'webui' should be removed,
Ingress is enabled." This is pre-existing — `ingress: true` and `webui` have
coexisted here for a while — but this is the first PR to touch the add-on and
run the linter over it, so it blocks here.

cleanuparr was the only one of the repository's 56 ingress add-ons that set
`webui`; the other 55 omit it. Removing it matches both the linter and the rest
of the repo. "Open Web UI" goes through ingress, and port 11011 stays published
for direct access.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

cleanuparr/CHANGELOG.md

@@ -6,6 +6,9 @@
   path Cleanuparr's web UI builds its asset, API and SignalR URLs from, so they
   resolve under the ingress path instead of the Home Assistant root. Direct access
   on port 11011 is unchanged (#3084)
+- Remove `webui`, which the add-on linter rejects when ingress is enabled and which
+  the repository's other 55 ingress add-ons do not set; "Open Web UI" uses ingress
+  and port 11011 stays published
  
 ## 2.10.6 (2026-09-19)
 - Update to latest version from Cleanuparr/Cleanuparr (changelog : https://github.com/Cleanuparr/Cleanuparr/releases)

cleanuparr/config.yaml

@@ -92,4 +92,3 @@ schema:
 slug: cleanuparr
 url: https://github.com/alexbelgium/hassio-addons/tree/master/cleanuparr
 version: "2.10.6.1"
-webui: "[PROTO:ssl]://[HOST]:[PORT:11011]"