fix(ci): run coverage from py3 instead of json_infra

[gurukamath]

🗒️ Description

Run coverage report in the py3 environment instead of json_infra. Post #1666 we run json_infra tests selectively based on which part of the codebase a particular PR touches. This could lead to wildly fluctuating coverage reports.

🔗 Related Issues or PRs

#1666

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx tox -e static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.06%. Comparing base (519eb26) to head (b237843).
⚠️ Report is 1 commits behind head on forks/osaka.

Additional details and impacted files

@@               Coverage Diff                @@
##           forks/osaka    #1824       +/-   ##
================================================
+ Coverage        53.45%   87.06%   +33.61%     
================================================
  Files              743      541      -202     
  Lines            44076    32832    -11244     
  Branches          3891     3015      -876     
================================================
+ Hits             23559    28586     +5027     
+ Misses           20306     3598    -16708     
- Partials           211      648      +437     

Flag	Coverage Δ
unittests	87.06% <ø> (+33.61%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.