Check consistency with Q-CTRL information and backend list to be updated

[acastellane]

URL to the relevant guide or resource

https://quantum.cloud.ibm.com/docs/en/guides/q-ctrl-performance-management
versus
https://docs.q-ctrl.com/fire-opal/discover/start-using/get-started-with-fire-opal-on-ibm-quantum?organization=nersc-lbnl

Select all that apply

• new content request
• typo
• code bug
• out-of-date content
• broken link
• other

Describe the fix or the content request.

Required libs and available backends at least must be up to date.
Thanks for checking overall consistency

For new content requests - if the request is accepted, do you want to write the content?

I only want to review the material when it's finished

[abbycross]

@acastellane does this one appear to be resolved? Looks like the available backends include new ones.

[acastellane]

• From the latest tests I ran, I see that variable backend_name is not defined.

• After

Supported backends: Run the following code to see the list of backends that are currently supported. If your device is not listed, reach out to Q-CTRL to add support.

the service.backends() routine cannot be run as catalog is not a QiskitRuntimeService service.

[pandasa123]

@abbycross, I think the code snippet should be updated to the following:

from qiskit_ibm_runtime import QiskitRuntimeService
 
service = QiskitRuntimeService()
service.backends()

CC: @chongyouquan, in case there's a different way you believe this should be done

[abbycross]

With @pandasa123 's suggestion I can get the entire notebook to run without error. @acastellane can you check and make sure the same is true for you?

See fix in #4756

[acastellane]

I have one question, I'm afraid the backends available associated with the service = QiskitRuntimeService() will be the backends I can access with my account, but maybe not the ones serverless can run on ? but I may be wrong.
In any case we provide a list of supported backends, which has no chance to match users' list. So there is a point to clarify here also.

[abbycross]

Correct, I think it is true that all supported backends are not necessarily the ones any one user can access, so since you think that could be confusing to a user to see a different list as an output, I can add a line to clarify this

[abbycross]

@acastellane how does this look?

[acastellane]

I'm still not comfortable in the guide with the explanation of the difference between the list of supported backends and the list of backends I can use (with some of them being not supported, from what I understand)