QVAC-23254 chore: release @qvac/translation-nmtcpp 0.8.0

[RamazTs]

🎯 What problem does this PR solve?

@qvac/translation-nmtcpp 0.7.0 was published to npm on 2026-08-12 (dist-tag release-0.7), but the package's pre-renumbering 2025 lineage still owns 0.7.1 on npm (published 2025-10-14, old pre-TypeScript API). Because 0.7.1 > 0.7.0, normal semver ranges around the current release (^0.7.0 / ~0.7.0) resolve to the obsolete 2025 artifact instead of the current one. npm never allows republishing a version, so 0.7.1 can never be reclaimed — the 0.7.x line is permanently poisoned for range resolution.

📝 How does it solve it?

• Bumps packages/translation-nmtcpp/package.json version 0.7.0 → 0.8.0.
• Adds a 0.8.0 CHANGELOG entry documenting that this is a content-identical republish of 0.7.0 under a collision-free version line (no code changes).
• 0.8.x has no historic versions on npm (verified), so consumers can depend on ^0.8.0 and get normal range semantics.

After merge, the npm publish requires pushing a release-translation-nmtcpp-0.8.0 branch per the release pipeline. Once 0.8.0 is live, the stray 0.7.0 on npm should be deprecated so nobody pins to the collided line.

[github-actions]

Review Status

Current Status: ✅ APPROVED
Approvals so far: Team Lead: 1, Member: 1

[github-actions]

License compliance — clean

No new dependency license findings in this PR.

Warn-only (shadow) mode — this check does not block merges yet.

Updated automatically by the canonical license compliance workflow.

NOTICE presence (advisory)

Missing NOTICE (advisory, does not block):

• ./.github/actions/release-merge-guard
• ./docs/website
• ./packages/ggml-coload-smoke
• ./packages/fabric/test/integration
• ./packages/inference-addon-cpp/mobile
• ./packages/sdk/e2e
• ./packages/llm-llamacpp/benchmarks/performance
• ./packages/llm-llamacpp/benchmarks/server
• ./packages/vla-ggml/sim/server
• ./packages/embed-llamacpp/benchmarks/performance
• ./packages/embed-llamacpp/benchmarks/server
• ./packages/asr-ggml/benchmarks/server