fix(module): include per-version changelog in release image

[universal-itengineer]

Description

The Deckhouse console showed no changelog for any virtualization module release: the changelog it renders is read from a changelog.yaml file inside the release image, and that file was never packaged into the image. The release image now carries the per-version changelog, so it shows up in the console's release list.

Why do we need it, and what problem does it solve?

Users open a module release in the console (Updates → Releases → Changelog) to see what changed between versions. For virtualization that panel was always empty — the release image only shipped version.json and module.yaml. Reported for v1.9.1, but it affected every release.

What is the expected result?

After a release build, the release:<tag> image contains changelog.yaml with the entry for that version, and the console shows the changelog for each release instead of an empty panel.

Example

The build reshapes CHANGELOG/CHANGELOG-<tag>.yml into the unified console format (features/fixes/chore → readable category → entries, with the PR linked). Empty types/categories are dropped, so a release that only touches one type renders cleanly.

Source — CHANGELOG/CHANGELOG-v1.9.1.yml (excerpt):

core:
  fixes:
    - summary: Update VMOP migration elapsed time every ten seconds while migration is in progress.
      pull_request: https://github.com/deckhouse/virtualization/pull/2495
vd:
  fixes:
    - summary: Fixed cancellation of virtual disk storage class changes and cancellation of local disk migration.
      pull_request: https://github.com/deckhouse/virtualization/pull/2502

Generated changelog.yaml shipped in release:v1.9.1 (rendered by the console):

fixes:
  Core:
    - Update VMOP migration elapsed time every ten seconds while migration is in progress. ([#2495](https://github.com/deckhouse/virtualization/pull/2495))
    - Select VirtualDisk migration target PVC strictly to avoid using an unrelated PVC. ([#2493](https://github.com/deckhouse/virtualization/pull/2493))
    - Fix metadata patch failing with "the server rejected our request" for objects without finalizers, labels or annotations. ([#2479](https://github.com/deckhouse/virtualization/pull/2479))
  Virtual disks:
    - Fixed cancellation of virtual disk storage class changes and cancellation of local disk migration. ([#2502](https://github.com/deckhouse/virtualization/pull/2502))
  Virtual machines:
    - Fixed an issue that prevented a VM from starting after a failed migration of a disk on local storage. ([#2509](https://github.com/deckhouse/virtualization/pull/2509))
    - Fixed live migration of VMs with disks on local storage attached via VirtualMachineBlockDeviceAttachment (hotplug). The target node no longer matches the source node. ([#2508](https://github.com/deckhouse/virtualization/pull/2508))
    - Fixed a false reboot requirement for VMs with only the Main network after upgrading to v1.9.1. Such VMs now do not receive the RestartRequired status if their configuration has not actually changed. ([#2475](https://github.com/deckhouse/virtualization/pull/2475))

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: module
type: fix
summary: The module changelog is now shown in the Deckhouse console for each release.