feat(docker): bundle homecore-server (HOMECORE / ADRs 126-134) in the image

The HOMECORE native Rust port of Home Assistant landed in v0.10.0
(PR #800). The published Docker image now ships its binary alongside
sensing-server and cog-ha-matter so a single `docker run` brings up
the full RuView + HA-wire-compatible stack.

Dockerfile.rust:
  - cargo build --release -p homecore-server in the build stage
  - strip the new binary
  - copy /app/homecore-server in the runtime stage
  - sanity-check: image build now fails if /app/homecore-server isn't
    executable (same guard pattern that already covers sensing-server
    and cog-ha-matter)
  - EXPOSE 8123 (HA-compat REST + WebSocket port — homecore-api
    binds 0.0.0.0:8123 by default per its --bind CLI flag)

docker-entrypoint.sh:
  - new dispatch keyword: `homecore` or `homecore-server`
    Usage: docker run --network host ruvnet/wifi-densepose:latest homecore
    Defaults --bind to 0.0.0.0:8123 (overridable via HOMECORE_BIND env)

The existing two dispatch paths (no arg → sensing-server, `cog-ha-matter`
→ HA + Matter cog) keep working unchanged. Three-binary image, one
entrypoint, operator picks the role at run time.

Triggers a workflow rebuild on push to main per the docker workflow's
path filter; the multi-arch (amd64 + arm64) image will be published
to Docker Hub as `ruvnet/wifi-densepose:latest` after CI green.

Refs ADRs 126-134, v0.10.0 release.

Co-Authored-By: claude-flow <ruv@ruv.net>

docker/docker-entrypoint.sh

@@ -28,6 +28,14 @@ case "${1:-}" in
             --sensing-url "${SENSING_URL:-http://127.0.0.1:3000}" \
             "$@"
         ;;
+    homecore|homecore-server)
+        # Route to the HOMECORE native Rust port of Home Assistant
+        # (ADRs 126-134, v0.10.0). Default bind matches HA at :8123.
+        shift
+        exec /app/homecore-server \
+            --bind "${HOMECORE_BIND:-0.0.0.0:8123}" \
+            "$@"
+        ;;
 esac
 
 # If the first argument looks like a flag (starts with -), prepend the