Fix bad release-notes section (backport #12153)

[mergify]

Summary

This causes failures in the docs build since #11855 merged (which just exposes them - it wasn't the cause), though I'm slightly confused as to why it doesn't always seem to cause failures, nor why it didn't fail the docs build for 1.0.

Details and comments

---

This is an automatic backport of pull request #12153 done by [Mergify](https://mergify.com).

[qiskit-bot]

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

• @Qiskit/terra-core

[coveralls]

Pull Request Test Coverage Report for Build 8597273474

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 10 unchanged lines in 3 files lost coverage.
• Overall coverage increased (+0.02%) to 89.312%

---

Files with Coverage Reduction	New Missed Lines	%
crates/qasm2/src/expr.rs	1	94.03%
crates/qasm2/src/lex.rs	3	93.13%
crates/qasm2/src/parse.rs	6	97.61%

Totals
Change from base Build 8574125408:	0.02%
Covered Lines:	58906
Relevant Lines:	65955

---

💛 - Coveralls