Use hashbrown::HashSet instead of ahash::HashSet

[mtreinish]

Summary

In the target_transpiler/mod.rs module we were using ahash::HashSet for a hash set implementation, but the rest of Qiskit has standardized on using hashbrown for the HashSet and HashMap types. Hashbrown uses ahash for it's hashing algorithm but it also provides other advantages. To ensure that hash sets are compatible across the library we should be using the same library for everything. To support this goal, this commit also adds a clippy rule that raises a warning if the std library hashmap or hashset is used, or the versions from ahash. This means with our current dependency set the only allowed hashset types are hashbrown::HashMap/HashSet and indexmap::IndexMap/IndexSet (for where we need to maintain insertion order). Ideally we'd have a rule that forces the use of ahash with IndexMap and IndexSet (see #12935) but I don't think clippy exposes an option to enable something like that.

Details and comments

[qiskit-bot]

One or more of the following people are relevant to this code:

• @Qiskit/terra-core
• @kevinhartman
• @mtreinish

[raynelfss]

This is sensible to me, there's still a lot of confusion as to which Mapping or Collection structures to use. This should allow us to be more consistent about allowing certain things.

[coveralls]

Pull Request Test Coverage Report for Build 10372610940

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 8 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.005%) to 89.66%

---

Files with Coverage Reduction	New Missed Lines	%
crates/qasm2/src/lex.rs	2	91.73%
crates/qasm2/src/parse.rs	6	96.23%

Totals
Change from base Build 10357074988:	0.005%
Covered Lines:	67392
Relevant Lines:	75164

---

💛 - Coveralls