TST: Remove pyargs from toxenv

[pllim]

This PR to remove pyargs from toxenv because it is now used in everything. I do not think we need !pyargs. Indirect follow-up of #9545

Tasks

• If you have a specific reviewer in mind, tag them.
• add a build milestone, i.e. Build 12.0 (use the latest build if not sure)
• Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see changelog readme for instructions)
  • update or add relevant tests
  • update relevant docstrings and / or docs/ page
  • start a regression test and include a link to the running job (click here for instructions)
    • Do truth files need to be updated ("okified")?
      • after the reviewer has approved these changes, run okify_regtests to update the truth files
• if a JIRA ticket exists, make sure it is resolved properly

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (8160ced) to head (0f95622).
⚠️ Report is 415 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #9550       +/-   ##
==========================================
- Coverage   80.66%   0.00%   -80.67%     
==========================================
  Files         368     368               
  Lines       37294   37224       -70     
==========================================
- Hits        30085       0    -30085     
- Misses       7209   37224    +30015     

☔ 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.

[braingram]

If switching all runs to pyargs is preferred some test changes will be needed. With this PR fewer tests are being run:
https://github.com/spacetelescope/jwst/actions/runs/15688696764/job/44198349903?pr=9550
=========== 3209 passed, 942 skipped, 1 xfailed in 724.24s (0:12:04) ===========
compared to on main:
https://github.com/spacetelescope/jwst/actions/runs/15688669586/job/44198243232
=========== 3361 passed, 942 skipped, 1 xfailed in 794.86s (0:13:14) ===========

[pllim]

skipped didn't increase... I will need to inject -v on both sides to see what is really missing.

The other side: https://github.com/spacetelescope/jwst/actions/runs/15691575132/job/44207821448?pr=9553

[pllim]

@braingram , look better now?

[braingram]

Thanks! Test numbers look to match. What wasn't being included that required the namespace packages? Given the impending build and that this changes the CI my vote is to wait until after the release.

[pllim]

Hard to tell at a glance. Will have to extract the test names and sort them and compare. But since you want to wait, there is no rush to do this. Thanks!

[pllim]

OK I think I figured out why. The tests folders in charge_migration and skymatch do not have __init__.py files to declare themselves for discovery. Let me push some commit(s) and see.

[pllim]

The test count now is same as main: 3361 passed, 942 skipped, 1 xfailed

[melanieclarke]

LGTM -- I'll go ahead and get this in.

[tapastro]

@meeseeksdev backport to release/1.19.x