Update Changelog 1.9

[jstriebel]

What this PR does / why we need it:
The upgrade from version 1.9.3 to 1.9.4 included a breaking change (#58720), namely Changes secret, configMap, downwardAPI and projected volumes to mount read-only.

This change was added to the changelog in the part Other notable changes, and not in Action Required, which is usually the case with breaking changes. This PR moves it there.

For reference: this change was discussed in #62099.

Release note:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jstriebel
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: bgrant0607

If they are not already assigned, you can assign the PR to them by writing /assign @bgrant0607 in a comment when ready.

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

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

[neolit123]

thanks for the update.
/ok-to-test

[jstriebel]

/retest

[jstriebel]

/test pull-kubernetes-e2e-kops-aws

[jstriebel]

/retest

[jstriebel]

/retest

[jstriebel]

/assign @bgrant0607

[jstriebel]

I lost track of this PR before, now everything is merged again.
Could anybody of you review this please? @neolit123 @bgrant0607 @thockin @lavalamp

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[jstriebel]

@neolit123 Should this still be merged?

[neolit123]

sadly, i do not know the policy on that.
you can ask in the #sig-release channel on slack.

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.