Address markdown format symbols in PR release note block?

[xiangpengzhao]

Some PRs' release notes have markdown format symbols (e.g., -, *), this leads to bad format in the CHANGELOG (see 1.9 changelog).

kubernetes/kubernetes#54175
kubernetes/kubernetes#52792
kubernetes/kubernetes#53043

We may not avoid PR authors to use such symbols, so should we address this case in the release note tool? @roycaihw

/cc @enisoc @david-mcmahon @Bradamant3

[roycaihw]

PR authors use symbols like - and * for multi-line release notes (kubernetes/kubernetes#54443). It's not clear how are we going to deal with them in current CHANGELOG.
And some release note with unintended newlines (\r\n) can also leads to bad formatting (kubernetes/kubernetes#54177)

These might become worse after we introduce the hierarchical release note(kubernetes/release#435) which uses indention to format the release note.

One possible solution is to squash release note into one line, by removing \r\n and leading -/* in each line.

[xiangpengzhao]

It'd be better to take care of this case. Otherwise we should send PR to fix the format in CHANGELOG manually.

[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
/remove-lifecycle stale

[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