Fix lurking qiskit.tools usage

[jakelishman]

Summary

A few places in docstrings where we'd left in references to qiskit.tools. At least one of these was executed as part of the documentation build, so was causing failures that weren't being caught because tox is currently building an invalid environment for the docs for Qiskit 1.0.

Details and comments

These are true Qiskit-1.0 bugs that fixing the tox environment in #11621 found.

[qiskit-bot]

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

• @enavarro51
• @Qiskit/terra-core

[sbrandhsn]

LGTM, I suspect random_unitary is now always available when make_circuit_ring is called and seed_mapper is simply not used anymore or seeded by seed_transpiler? Do you think seed_mapper should also be removed from randomized_benchmarking.py?

[coveralls]

Pull Request Test Coverage Report for Build 7625560079

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.01%) to 89.502%

---

Totals
Change from base Build 7623118598:	-0.01%
Covered Lines:	59489
Relevant Lines:	66467

---

💛 - Coveralls

[jakelishman]

Yeah, the old qiskit.tools.qi.qi (or whatever it was) is from years ago - before I joined IBM, and seed_mapper is what the argument to transpile (and execute, at the time) used to be called similarly years ago.

Thanks for spotting those other imports - yeah, it makes sense to squash them all at once. asv may start a new trace for those test files due to modification of the test, but I'm not 100% sure if it counts stuff in the imports towards the hash of the tests. It's not a big deal, just probably best to get everything squashed in one go.

[mtreinish]

We won't be able to use the benchmarks with Qiskit pre-0.10.0 anymore (I remember adding that logic when the interface changed), but I guess that doesn't matter :)