Prepare 2.2.0b1 release

[raynelfss]

Summary

These commits will temporarily change the version strings from 2.2.0 to 2.2.0b1 in preparation for tagging the 2.2.0b1 beta release.

Details and comments

Waiting for:

• Transpile C API #14760

[coveralls]

Pull Request Test Coverage Report for Build 17302538518

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 142 unchanged lines in 9 files lost coverage.
• Overall coverage increased (+0.05%) to 88.452%

---

Files with Coverage Reduction	New Missed Lines	%
crates/circuit/src/parameter/parameter_expression.rs	1	82.8%
crates/qasm2/src/expr.rs	1	93.63%
crates/qasm2/src/lex.rs	1	93.04%
crates/cext/src/exit_codes.rs	6	33.33%
crates/qasm2/src/parse.rs	6	97.56%
crates/transpiler/src/passes/commutation_cancellation.rs	14	91.43%
crates/transpiler/src/transpile_layout.rs	17	97.72%
crates/transpiler/src/passes/vf2/vf2_layout.rs	40	91.18%
qiskit/circuit/quantumcircuit.py	56	93.8%

Totals
Change from base Build 17293270440:	0.05%
Covered Lines:	91007
Relevant Lines:	102888

---

💛 - Coveralls

[qiskit-bot]

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

• @Eric-Arellano
• @abbycross
• @beckykd
• @Qiskit/terra-core

[jakelishman]

We need to update crates/cext/cbindgen.toml to bump the version to 2.2.0.

We don't actually have a field in there for marking a beta release - I think we discussed it, but presumably we decided not to include it in the end.

[mtreinish]

We need to update crates/cext/cbindgen.toml to bump the version to 2.2.0.

We don't actually have a field in there for marking a beta release - I think we discussed it, but presumably we decided not to include it in the end.

I think we should just add it there is clearly a spot for it with 0xb. I think when I reviewed it my brain might have autocompleted it being there, I was surprised it was missing.

[jakelishman]

oh wow haha - apparently I had a branch checked out that didn't include #14576!