Migration guide for providers to implement V2 primitives

[ElePT]

This is a proposal for content to address #2469. After a brief discussion with @jyu00 we agreed that we should focus this migration guide on showing how to implement new primitives for providers. However, I have not been involved in all discussions regarding the vision for this migration (and conversations around backend.run tend to raise a lot of different opinions) so I would appreciate confirmation that the content proposed fits the direction we want to show.

The page is currently in a pretty raw state, missing formatting, API ref links, a review on the titles, capitalization, etc, but I wanted to open a PR as fast as possible to ask for opinions on including the backend primitive wrappers as a tool for provider migration. This idea came from inspecting the only instance I know of external provider beyond the immediate product sphere, which is https://github.com/qiskit-community/qiskit-aqt-provider/tree/master, and subclasses backend primitives to expose their own primitive implementations. Following this, I decided to structure the page as follows:

• motivation: @jyu00 mentioned this was often requested by users, I tried to keep it short and touch on the usefulness of the abstraction level of the primitives
• Backend primitives as a migration alternative for providers that already implemented backend.run (following the AQT example)
• Custom primitives as an alternative for providers that want it, or didn't implement backend.run (following the StatevectorSampler and StatevectorEstimator) examples

Please let me know if you have any other take on how the content should look like @javabster, @jyu00.

[abbycross]

One last question to resolve and then I think it's ready to go

[jyu00]

Some minor suggestions for consistency, but otherwise looks good!

[jyu00]

ok... but why is it called Transition to the Qiskit Runtime provider? Is it meant to say transitioning from qiskit-ibmq-provider / qiskit-ibm-provider to qiskit-ibm-runtime ?

[jyu00]

@abbycross how come some of the links were added to open new tabs but the rest are not? Is there a standard on what should / should not open a new tab?

[abbycross]

@abbycross how come some of the links were added to open new tabs but the rest are not? Is there a standard on what should / should not open a new tab?

All external links. (i.e., not coming from an IBM repo) will open in a new tab. Therefore, the ones from https://qiskit.github.io/ will all have that external-link arrow. I see that the last link in your screenshot should have been an internal link - I missed that in my review! Fixed it.
Note that links to the UI (like to the compute resources, page, the dashboard, etc.) should be linked to with the whole URL and will render as an external link.

[beckykd]

Thanks, Elena!

[abbycross]

Has this comment been resolved? This PR has gotten too noisy to be absolutely sure :-)