Prepare 1.3.0 release

[raynelfss]

• Move loose release notes.

Summary

The following commits set the version number on stable/1.3 to 1.3.0 in preparation for the 1.3.0 final release.

Details and comments

The following commits will:

• Set the version number to 1.3.0.
• Consolidate any loose release notes into the releasenotes/notes/1.3/ folder.
• Update the cargo dependencies.
• Fix any typos, broken links, and bad references in the folder releasenotes/notes/1.3/.
• Include a prelude release note for the release.

[qiskit-bot]

One or more of the following people are relevant to this code:

• @Eric-Arellano
• @abbycross
• @beckykd
• @Qiskit/terra-core

[beckykd]

Lots of good stuff! let me know if you have any questions!

[raynelfss]

I have checked all release notes to the best of my abilities now. @beckykd feel free to further review these. I should be posting the prelude release note sometime tomorrow.

[beckykd]

I think I'm through everything! Thanks for putting them all together and doing that initial edit!

[beckykd]

I'm not sure what the term "inlined" means. Can you rephrase?
"inlined onto the base circuit"

[raynelfss]

I believe it's just mentioning how it's realigning new instructions onto a base circuit. Maybe the word re-align works better?

[jakelishman]

"Inline" is a compiler term

[jakelishman]

But also I think that note is from some prior release?

[mtreinish]

Thanks for doing this, I've done a quick first pass through the notes but I still need to read the rendered output in sphinx to see how the complete notes read. From this first pass though I have a few concerns before I feel this is ready to merge and subsequently tagging the release.

The first is there are some notes that are already published on prior releases we need to delete those files from the stable/1.3 branch in this PR to avoid duplicating them. You can just git rm these files, but please do an audit of all the notes in the rendered output to make sure none exist on https://docs.quantum.ibm.com/api/qiskit/release-notes/1.2 or https://docs.quantum.ibm.com/api/qiskit/release-notes/1.1

The second large concern is around how we're documenting performance improvements. We are very inconsistent about how we're reporting speedups across the board. A lot of synthesis functions are called out individually as having been ported to rust and citing a speedup factor. While for the transpiler passes only some do this, the basis translator stands out prominently as being one of the few that did this. If we're going to call these out as feature notes we should be consistent and ensure we do it for all of them. Or if we feel it's not important to document them individually as a long list it is probably better to consolidate the multiple notes into a single note for passes that lists out the passes we've ported to rust and they're generally faster. We should do the same thing for synthesis functions too. Personally I think a single large note documenting all of them is better for readers than doing a lot of small notes.

A smaller thing is I feel like many release notes were not checked over for completeness or correct categorization and we should ensure this is all correct before publishing the release notes.

[mtreinish]

Thanks for updating things. I started with the updated prelude, it is looking much better. Just have some small wording suggestions or missing details in suggestions

[mtreinish]

I think this looks good now, while probably not perfect (no release's documentation is ever perfect) it's definitely looking really good to me now.. Thanks for all the work on polishing it and updating all the notes and also shepherding the 1.3.0 release.