docs: reflect pending SenseVoice license confirmation

[LauraGPT]

Summary

Align the English and Chinese README license sections with the actual status of SenseVoice #334.

The READMEs currently present the early response as an official, completed clarification. The same maintainer later reopened the issue for license-owner/core-maintainer confirmation, explicitly saying that the earlier answer should not substitute for that confirmation. The issue remains open.

• Replace the final-authorization wording with a link to the ongoing discussion and the reopening follow-up.
• Preserve the source-code MIT distinction, official model-card link, and immutable v1.1 model-license reference.
• Update the documentation regression tests to reflect the pending-confirmation status and prevent the earlier response from being presented as final authorization.

Scope

• No model behavior changes.
• Three files only: two READMEs and their existing documentation test.
• No license text, grant, model artifact, model card, dependency, API, or workflow changes.
• This PR does not decide whether commercial use, private derivatives, ONNX redistribution, or any other use is permitted. Those questions still require the appropriate license-owner confirmation. It does not resolve Clarification: does MODEL_LICENSE §3 "reference and learning purposes only" restrict commercial use? / 关于 §3 与商用边界的确认 #334 or License clarification for SenseVoice-Small weights at a fixed revision (ONNX redistribution) modelscope/FunASR#3715.

Validation

• Regression tests first: 2 expected failures and 1 pass against the existing README wording.
• After the documentation correction: 14 tests passed across test_license_clarification.py, test_whats_new.py, test_canonical_qwenaudio_links.py, test_github_templates.py, and test_funasr_requirement.py.
• python -m unittest tests.test_container_contract tests.test_device_env: 14 passed.
• Both changed Markdown documents parsed successfully with markdown-it-py; git diff --check passed.
• Self-reviewed against the live issue comments. No model inference, GPU, service, or legal-interpretation verification is claimed.

Signed and DCO-signed-off. Prepared with Codex assistance. No merge or image publication is requested without the separate applicable authorization and normal repository checks.