[AbeCoull]

Issue #, if available:

Description of changes:
adds in a circuit validation suite to github actions and tox

Testing done:

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the CONTRIBUTING doc
• I used the commit message format described in CONTRIBUTING
• I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (dde04f3) to head (1991cb6).
⚠️ Report is 33 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #361   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           49        49           
  Lines         4771      4771           
  Branches       539       539           
=========================================
  Hits          4771      4771           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[aniksd-braket]

This is a great extension to our testing capability. My one concern would be the time it would now take to run our CI tests, do you have any insights/metrics into that?

[aniksd-braket]

Why can't we use result.measurement_probabilities in this function, and then filter out based on n_qubits

[rmshaffer]

This is a great extension to our testing capability. My one concern would be the time it would now take to run our CI tests, do you have any insights/metrics into that?

They're actually run in this PR itself. Looks like the new integ-tests took only about 1 minute.