fix: bump CI rsfusa pin from v0.3.10 to v0.3.17

[SoundMatt]

Summary

Bumps the ASIL-B safety job's rsfusa install pin across the 7-release gap
(v0.3.10 -> v0.3.17, latest). Pure CI-tool-pin bump, no source changes.

Verification

Installed rsfusa v0.3.17 locally the same way CI does
(cargo install --git https://github.com/SoundMatt/rust-FuSa --tag v0.3.17 rsfusa --locked)
and ran every command the safety job runs, against this repo's own tree,
for real (not relying on the || true masking in ci.yml).

No new ERROR-level findings vs v0.3.10.

• The two gates in this job that are not masked by || true
  (qualify, release) pass cleanly under both v0.3.10 and v0.3.17, with
  identical results:
  • qualify: 16/16 cases passed, badge unqualified (same as before)
  • release: SBOM (82 components), provenance, artifact manifest all
    written successfully
• The || true-masked commands (lint, analyze, check, trace,
  fmea, tara, cyber) all hit the same
  parse error: missing field 'standard' against this repo's .fusa.json
  under v0.3.17 that they already hit under v0.3.10 — confirmed by
  installing v0.3.10 side-by-side and re-running the same commands. This
  repo's .fusa.json predates that config schema; it's a pre-existing,
  CI-masked issue, unrelated to and not introduced by this pin bump. Out of
  scope for this PR (which is scoped to the pin bump only) — flagging for
  visibility.
• comp also behaves identically between versions (exit 1, one function
  parse_schedule_tables at cyclomatic complexity 11 > threshold), also
  pre-existing and || true-masked, not new.
• Checked rust-FuSa's v0.3.10..v0.3.17 changelog for anything else
  relevant: v0.3.11/12 spec conformance updates, v0.3.13 qualify-hash fix,
  v0.3.15 fix for the verify/--test-output=immediate bug (confirmed
  fixed — rsfusa verify --dir . now exits 0 cleanly against this tree,
  156/156 tests), v0.3.16 argument-injection/UTF-8-panic security fixes
  (affect impact/truncate, neither used by this job) plus rust-FuSa's
  own CI gate-masking cleanup (rust-FuSa's own repo, not ours), v0.3.17
  Docker builder fix (not applicable here). None of these change behavior
  against rust-LIN's tree.

Local build/test

• cargo build --release — clean
• cargo test — 48 passed (46 unit/integration + 2 doctests), 0 failed
• cargo clippy --all-targets -- -D warnings — clean
• cargo fmt --check — clean

Version bump

None. Precedent: #11 (the original v0.3.10 pin) was also a pure CI-pin
change with no Cargo.toml bump.