refactor(hermes): drop config health check scanner

The Hermes config.yaml schema has stabilized and users have migrated to
the current provider fields, so the value of scanning for model.provider
dangling references, custom_providers shape errors, v12 migration residue
etc. no longer justifies the maintenance surface — and the scan produces
false positives when users keep some providers under Hermes' v12+
providers: dict (Hermes' runtime merges both shapes, but CC Switch's
scanner only looked at the list form).

Removes the whole HermesHealthWarning type, scan_hermes_config_health
command, HermesHealthBanner React component, useHermesHealth hook,
warnings field on HermesWriteOutcome, and the three helper functions
(yaml_as_non_empty_str, collect_mapping_string_keys, hermes_warning)
that only served the scanner. Drops the matching i18n keys in
zh/en/ja and the fixInWebUI button label that only the banner used.

src/lib/api/hermes.ts

@@ -1,6 +1,5 @@
 import { invoke } from "@tauri-apps/api/core";
 import type {
-  HermesHealthWarning,
   HermesMemoryKind,
   HermesMemoryLimits,
   HermesModelConfig,
@@ -12,19 +11,15 @@ import type {
  * CC Switch intentionally keeps its Hermes surface minimal — deep configuration
  * (model, agent behavior, env vars, skills, cron, logs, analytics) lives in
  * the Hermes Web UI at http://127.0.0.1:9119. CC Switch only reads the `model`
- * section to highlight the active provider, scans config health, and launches
- * the Hermes Web UI for everything else. Writes to `model` happen implicitly
- * via `apply_switch_defaults` when the user switches providers.
+ * section to highlight the active provider and launches the Hermes Web UI for
+ * everything else. Writes to `model` happen implicitly via
+ * `apply_switch_defaults` when the user switches providers.
  */
 export const hermesApi = {
   async getModelConfig(): Promise<HermesModelConfig | null> {
     return await invoke("get_hermes_model_config");
   },
 
-  async scanHealth(): Promise<HermesHealthWarning[]> {
-    return await invoke("scan_hermes_config_health");
-  },
-
   /**
    * Probe the local Hermes Web UI and open it in the system browser.
    * Optional `path` lets callers deep-link to specific pages like `/config`.