Cockpit readiness: add version and release lens

[smota]

Background & Problem Statement

Epic: #156

Merged is not always delivered. Cockpit should show version/release state so users understand whether a goal is awaiting release, included in a version, or has no release impact.

Proposed Solution

Add Version/Release Lens to goal summary and detail.

Requirements

• Infer/display target branch.
• Infer/display release impact: none, docs-only, patch, minor, major, internal-only, unknown.
• Show awaiting-release state from labels/branch/PR state where inferable.
• Show candidate version if available from release/versioning helpers.
• Show release note needed/not-needed/recorded.
• Preserve vs semantics.

Acceptance criteria

• Goal summary includes version/release state.
• Detail explains release impact and evidence/source.
• Awaiting-release label/state appears when applicable.
• Docs explain merged vs delivered distinction.

Test plan

• Unit tests for merged-to-development awaiting-release, closed trunk goal, docs-only impact, no-release-impact.
• UI snapshot for version lens.

Workflow classification

Product/domain issue.

[github-actions]

Integrated into development by PR #155: #155

Merge commit: aefe4d9f7d159ccf04d29a4490c4b1c40269e81c
Release/promotion to main is tracked separately.