chore: bundle the November dependency updates #30

What

Apply the five open Dependabot updates in one pull request, with their lock files corrected:

• chore(deps): Bump prom/prometheus from v3.15.0 to v3.15.1 in the compose-images group #23 prom/prometheus v3.15.0 to v3.15.1
• chore(deps): Bump node from 22.23.3-alpine to 22.23.4-alpine in /src/frontend in the other-images group across 1 directory #24 node 22.23.3-alpine to 22.23.4-alpine
• chore(deps): Bump @angular/cli from 21.2.27 to 21.2.28 in /src/frontend in the angular group #25 @angular/cli 21.2.27 to 21.2.28
• chore(deps): Bump postcss from 8.5.30 to 8.5.31 in /src/frontend in the npm-minor-patch group #26 postcss 8.5.30 to 8.5.31
• chore(deps): Bump the nuget-minor-patch group with 2 updates #27 Markdig 1.4.1 to 1.5.0 and Swashbuckle.AspNetCore 10.3.0 to 10.3.1

Why

Every push to develop deploys, so one bundle avoids five consecutive deployments. #25, #26 and #27 also cannot pass CI as generated: #25 and #26 drop @emnapi entries that npm ci needs, and #27 leaves the PkgDiff.Tests lock file on the old Markdig version.

Done when

• All five updates are on develop and the required CI checks pass
• chore(deps): Bump prom/prometheus from v3.15.0 to v3.15.1 in the compose-images group #23, chore(deps): Bump node from 22.23.3-alpine to 22.23.4-alpine in /src/frontend in the other-images group across 1 directory #24, chore(deps): Bump @angular/cli from 21.2.27 to 21.2.28 in /src/frontend in the angular group #25, chore(deps): Bump postcss from 8.5.30 to 8.5.31 in /src/frontend in the npm-minor-patch group #26 and chore(deps): Bump the nuget-minor-patch group with 2 updates #27 are closed as superseded