chore: rename internal `kip` identifier namespace to `skip`

[mairas]

Problem

The fork rebranded the product to Skip (@halos-org/skip) on the surface — package name, serving path, PWA manifest, branding — but the code-level identifier namespace was never rebranded. Internally everything is still kip:

• ~39 --kip-* CSS custom properties — --kip-contrast-color, --kip-zone-alarm-color, --kip-night-color, the whole theme token set.
• Directive selectors — kipGestures, kipScrollNav, kipResizeObserver.
• Runtime-generated ids — kip-gesture-inject-<uuid> (iframe widgets).
• Class names — e.g. the newly added .kip-app-shell shell wrapper.
• Service/file names & symbols — kip-series-contract, kip-series-api-client.
• User-visible log/error strings — "[Kip ...]", "requirement to run Kip".
• SVG icon reference — svgIcon="kip" (resolves to a kip symbol id inside assets/svg/icons.svg).

grep -riIl kip src matches ~190 files. There are zero skip- prefixed identifiers, so every new identifier that follows the existing convention (like .kip-app-shell) deepens the inconsistency.

Scope: rename kip → skip for runtime identifiers

• --kip-* CSS custom properties + every consumer (SCSS, templates, inline styles, theme files).
• Directive selectors + their usages across templates.
• Class names, generated element ids, service/file names, TS symbols.
• Log/error string literals (Kip/KIP → Skip/SKIP).
• svgIcon="kip" and the coupled kip symbol id in assets/svg/icons.svg — rename together or it silently breaks the icon.

Do NOT touch (hard boundaries)

• Persisted localStorage keys — already migrated to skip.* (skip.appConfig, skip.dashboardsConfig, skip.connectionConfig, skip.themeConfig) in src/app/core/constants/config-storage.const.ts. Leave them; do not re-migrate.
• Serving contract — @halos-org/skip package name, baseHref/serve-path /@halos-org/skip/, src/manifest.json id/scope/start_url. Already correct.
• Wire-format / applicationData config keys and configVersion — renaming these would break existing user configs. Runtime CSS vars and DOM ids are not persisted, so they are safe to rename.
• upstream (mxtommy/kip) references — remote name, cherry-pick notes, and inherited-doc mentions stay as-is; they name the actual upstream project.

Notes

• Large but mostly mechanical. Land as its own dedicated PR (or a small stack split by layer: CSS tokens / directives / strings-and-ids), not piecemeal alongside feature work.
• Verify no persisted-config or serving-path identifier is swept up — diff-review the non-.scss/.html hits specifically.
• Rename the SVG symbol id and its reference in the same commit.

Filed from the navigation-chrome work (#185), where a new .kip-app-shell class was added following the existing kip- prefix rather than introducing a lone skip- outlier.