Remove qiskit.test

[1ucian0]

Summary

Related to #6862

To be deprecated in 0.46 #11001

Details and comments

[coveralls]

Pull Request Test Coverage Report for Build 7726439144

Warning: This coverage report may be inaccurate.

We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 31 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.02%) to 89.572%

---

Files with Coverage Reduction	New Missed Lines	%
qiskit/exceptions.py	2	93.75%
crates/qasm2/src/lex.rs	5	91.94%
crates/qasm2/src/parse.rs	24	96.23%

Totals
Change from base Build 7721773451:	-0.02%
Covered Lines:	59308
Relevant Lines:	66213

---

💛 - Coveralls

[qiskit-bot]

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

• @enavarro51
• @Cryoris
• @Qiskit/terra-core
• @ajavadia
• @ikkoham
• @levbishop
• @mtreinish
• @nkanazawa1989
• @t-imamichi

[mtreinish]

Is the intent to remove all of qiskit/test or just qiskit/test/mock? The test changes and PR title make it sound like the former but the diff is only for the latter.

[jakelishman]

I had forgotten this PR existed, but I've made #11445 which replaces quite a bit of this PR - it removes large tracts of qiskit.test without moving the remaining components, so we can split off the "remove dead code" and "rename qiskit.test" components of our aims with qiskit.test.

This PR already has lots of merge conflicts, whereas #11445 should be rather easier to merge in that regard - it doesn't try to do the removals and the touch-every-test-file bit in the same PR.

[jakelishman]

I got weirded out when the GitHub diff didn't appear to show the removal of the qiskit/test directory, but it turns out that it's tracked each file in there as a rename, and that's just how it shows things.

I'm going to move this to merge now - it appears to be done correctly to me (barring last-minute lint/whatever). I think we could expand the release note, but we'll do that post rc1 when we sort out the rest of them, and this PR needs to get in the merge queue ASAP to avoid further conflicts arising.