Wrap release notes dependency subsection in dropdown

[torredil]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

The release-notes tool includes a dependency report by default, which provides valuable information about dependency changes between releases. However, this report can be quite lengthy and clutters the changelog, making it difficult for users to quickly scan the main changes (features, bug fixes, etc.).

Which issue(s) this PR fixes:

None.

Special notes for your reviewer:

Tested manually, see screenshots below for generated release notes diff.

• Without change:

• With change:

Does this PR introduce a user-facing change?

Wrap release notes dependency subsection in dropdown

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: torredil
Once this PR has been reviewed and has the lgtm label, please assign saschagrunert for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• cmd/release-notes/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[torredil]

@xmudrii Small QOL improvement PTAL 🙏

The motivation for this: we are currently using release notes tool to generate our CHANGELOG over at https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/CHANGELOG.md (and it works great!) however, the dependencies subsection is overwhelming. Rather than disabling it in the report, we'd like to add a dropdown, ty!

[xmudrii]

This looks good to me, thank you @torredil! But before we merge this, I have two questions:

• @saschagrunert -- is this something that could be integrated directly into go-modiff?
• @katcosgrove -- is this okay from the release team side? I'm not sure if this will affect k/k, but I assume it will.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

/remove-lifecycle stale