Fixing monitor tools

[1ucian0]

The tools in qiskit.tools.monitor are a bit neglected. This PR is trying to bring them up to speed.

qiskit.tools.monitor.job_monitor

Closes #7865

job_monitor now works with RuntimeJob. JobV1 does not provide queue_position so a general job_monitor should not assume it (probably was only a thing with IBMJob. If job_monitor stays in Qiskit, it should be generic.

qiskit.tools.monitor.backend_monitor

It was not working at all, so now it works. In the future, it should work with any BackendV2 or be moved to qiskit-ibm-runtime otherwise.

from qiskit_ibm_provider import IBMProvider
from qiskit.tools.monitor import backend_monitor
provider = IBMProvider()
backend_monitor(provider.get_backend('ibm_sherbrooke'))

ibm_sherbrooke
==============
Configuration
-------------
    n_qubits: 127
    operational: True
    status_msg: active
    pending_jobs: 139
    backend_version: 1.4.28
    basis_gates: ['ecr', 'id', 'rz', 'sx', 'x']
    local: False
    simulator: False
    backend_name: ibm_sherbrooke
    qubit_channel_mapping: [['d0', 'm0'
....

qiskit.tools.monitor.backend_overview

Similarly to qiskit.tools.monitor.backend_monitor, it was not working at all, so now it works. In the future, it should take a BackendV2 or be moved to qiskit-ibm-runtime otherwise.

from qiskit.tools.monitor import backend_overview
backend_overview()

TODO:

• if we keep them, a bugfix reno. we keep it in the 0.* major
• if we dont keep them, deprecate/remove them

[jakelishman]

Copying in some discussion from offline:

imo these functions aren't suitable for core Qiskit; information about queue positions and reading custom downstream fields from a Job subclass shouldn't be part of the core library, since it's not part of the Job interface. I think we ought to be moving this functionality to the relevant packages, where it can be maintained and update as the custom Job subclasses changes, or as the structure of the custom information about queue position changes.

[ElePT]

I agree with @jakelishman, moving this functionality out of qiskit would also be coherent with the changes laid out in #10266 (the fake backend epic).

[1ucian0]

It makes total sense what you are both saying.

I changed the base to stable/0.46 and I will add the deprecation warnings.

[jakelishman]

Best check overlap with some of Matt's recent PRs - #11513 and #11514 might cover these deprecations.

[1ucian0]

I'm merging the mtreinish:deprecate-tools into this one. So blocked by #11514 (tagging on hold).

[qiskit-bot]

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

• @Qiskit/terra-core

[jakelishman]

#11514 is merged now, removing hold.

[mtreinish]

Given the timeframe for the 0.46.0 release I've deferred this to 0.46.1, it's a valid bugfix for a patch release too.

[kevinhartman]

Looks good to me. The changes seem low risk given that the module they address does not currently work.