Update release notes draft to version v1.34.0-alpha.3

[ArvindParekh]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
This PR updates the Release Notes Draft to k/k v1.34.0-alpha.3

Which issue(s) this PR fixes:

Special notes for your reviewer:
This is an automated PR generated from krel The Kubernetes Release Toolbox

[Chewypewy]

Nicely done

[k8s-ci-robot]

@Chewypewy: changing LGTM is restricted to collaborators

In response to this:

Nicely done

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-sigs/prow repository.

[Chewypewy]

Best of 2023

[k8s-ci-robot]

@Chewypewy: changing LGTM is restricted to collaborators

In response to this:

Best of 2023

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-sigs/prow repository.

[wendy-ha18]

LGTM, seems like majority of alpha.3 were chore works to replacing deprecated package so not much comment on release notes from my side. And the maps and .md release note are still sync with each other (unless changing occur in maps later).

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArvindParekh, wendy-ha18

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:

• releases/release-1.34/OWNERS [wendy-ha18]

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

[wendy-ha18]

Also could you have a look in the lint check failed @ArvindParekh? one or a few .yaml files may not sastify the validation.

[wendy-ha18]

cc @Vyom-Yadav for support the review and approval quickly.

[ArvindParekh]

LGTM, seems like majority of alpha.3 were chore works to replacing deprecated package

@wendy-ha18 correct. Accordingly, many changes in this PR are simply changing single-quotes to backticks in those deprecated package messages, to basically better represent them during markdown. Some others are fixing tense and grammatical errors.

And the maps and .md release note are still sync with each other (unless changing occur in maps later).

I did update the map files to fix the failing tests, and have updated the .md and .json files manually to reflect those changes. Thanks!

[Vyom-Yadav]

/lgtm