ci(workspace): exclude hailo crates from core-and-rest shard (iter 230)

iter-219's workspace rejoin added 4 hailo crates to the root
workspace (hailort-sys, ruvector-hailo, ruvector-mmwave,
ruvector-hailo-cluster). The `core-and-rest` shard in ci.yml uses
`--workspace --exclude X` to catch every crate not in another
shard, so the hailo crates silently got pulled in.

This pushed core-and-rest's compile + test cycle past its 150-min
timeout — historical runs landed at 2h 30m exactly, the iter-228
+ iter-229 PR run hit 2h 30m 18s and was cancelled mid-test.
The hailo crates are independently gated by hailo-backend-audit.yml
(cargo-deny + cargo-audit + clippy + test on x86 default features
plus aarch64 cross-build) so excluding them from core-and-rest
doesn't lose coverage — it only stops the catch-all shard from
double-compiling them on every workspace push.

Failing job:
  Tests (core-and-rest) on PR #413 (a88edd6b9 / 9db4499a7):
    completed cancelled started=04:01:40 completed=06:31:58
    step #7: Run tests (core-and-rest) — cancelled at 150min
    step #8: Run doctests — skipped (never reached)

Same root cause as the iter-228 cargo-audit + iter-228 cross-build
breakages: a side effect of the iter-219 workspace rejoin that
only surfaces under specific CI matrix configurations.

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

.github/workflows/ci.yml

@@ -221,6 +221,10 @@ jobs:
               --exclude ruvector-graph-transformer
               --exclude ruvector-domain-expansion
               --exclude ruvector-robotics
+              --exclude hailort-sys
+              --exclude ruvector-hailo
+              --exclude ruvector-mmwave
+              --exclude ruvector-hailo-cluster
     steps:
       - uses: actions/checkout@v4