Prepare FunASR 1.4.17 release candidate

[LauraGPT]

Summary

Prepare the next non-empty Python release, 1.4.17, from main
e7e61293d308f4342ab9307895e710e4b51b949c. This PR changes only the package
version, release-version contract and candidate links in four READMEs and two
repository-role guides. The guides retain 1.4.16 as the current published release
and explicitly distinguish the unpublished candidate.

Merged changes since v1.4.16 include explicit PCM16 input, timestamp and hotword
corrections, speaker-inference sample-rate preservation, long-segment streaming
recovery, blank-line handling and accelerator fallback warnings. Unmerged PRs
are not included. No new GPU, model-inference or hardware performance claim.

Validation

• Signed commit with DCO: 241c1efb4dfa36139ef82b28ca6ee900d892c280.
• Exact candidate tree: 3bb1ba1096c6c273cd44c99bddf27a66a87288fd.
• Release-version contract first failed three assertions against 1.4.16, then
  passed after the candidate update.
• Focused release/runtime/package-data and CLI/API/reference-doc checks:
  60 passed, 1 skipped, 22 subtests passed. The skip is an optional Sphinx
  anchor check because Sphinx is absent; this is not a full repository suite.
• compileall and git diff --check passed.
• PEP 517 sdist and wheel builds passed in an existing isolated CPU environment
  with no dependency downloads. Its missing pytest-runner dependency was restored
  from an existing cached wheel whose SHA-256 matched PyPI metadata.
• Twine, offline/no-dependencies isolated installation, version metadata,
  13 console entry points and package data checks passed. No model was loaded.
• Candidate wheel SHA-256:
  46c5733f4623d31c3bb256e4eb1d398e41fb01db8ffda37faead2495d15a4138.
• Candidate sdist SHA-256:
  6c5ec2d2acdb3cd2272135996e21d32561ab8164b6674b73dcb01de663d6153f.

Release Gates

This PR is preparation, not a published release. No v1.4.17 tag, GitHub Release,
PyPI upload, website deployment or model-card/announcement publication has been
performed. The remote pre-release backup branch was created and its exact SHA
verified; the original source bundle/archive and candidate bundle/archive remain
preserved.

Main requires one independent approving review and enables Code Owner review.
Do not use administrator bypass or self-approval. Recheck exact head/base,
discussion resolution, CI and branch policy before merging or publishing.
Rebuild/reverify final merged/tagged source before using final publication assets.

The current runtime pointer is runtime-llamacpp-v0.2.6; the current repository
release script requires 10 runtime archives, including a separate CUDA
Blackwell archive. With wheel, sdist and SHA-256 manifest this is 13 assets,
not the historical nine-runtime/12-asset count. Keep the current exact matrix;
do not silently omit Blackwell. Runtime bytes and the final combined manifest
still need verification after review, before the irreversible PyPI step.