Remove historical versions from release notes (backport #11855)

[mergify]

See #11840 for context.

Note that we don't include release notes for dev docs in docs.quantum.ibm.com, so these release notes won't hit production. This is instead intended to help Qiskit developers check that release notes are valid well in-advance of release prep.

---

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

[mergify]

Cherry-pick of 2cbbe2b has failed:

On branch mergify/bp/stable/1.0/pr-11855
Your branch is up to date with 'origin/stable/1.0'.

You are currently cherry-picking commit 2cbbe2bee.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/release_notes.rst

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[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:

• @Eric-Arellano
• @javabster
• @Qiskit/terra-core