JP-3726: Resource Warnings when Using Multiprocessing

[kmacdonald-stsci]

Resolves JP-3726

This PR addresses when running the detector 1 pipeline, "No space left on device" and "warnings.warn('resource_tracker: There appear to be %d '" warnings appeared. On @melanieclarke's recommendation, I switched the multiprocessing from "forkserver" to "spawn" and those warnings disappeared.

Tasks

• update or add relevant tests
• update relevant docstrings and / or docs/ page
• Does this PR change any API used downstream? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)
  • run regression tests with this branch installed ("git+https://github.com/<fork>/stcal@<branch>")
    • jwst regression test
    • romancal regression test

news fragment change types...

• changes/<PR#>.apichange.rst: change to public API
• changes/<PR#>.bugfix.rst: fixes an issue
• changes/<PR#>.general.rst: infrastructure or miscellaneous change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.96%. Comparing base (068afd9) to head (0c329fd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #350   +/-   ##
=======================================
  Coverage   85.96%   85.96%           
=======================================
  Files          61       61           
  Lines       10333    10333           
=======================================
  Hits         8883     8883           
  Misses       1450     1450           

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

[melanieclarke]

Changes look good. In my local testing, this worked for me to avoid the resource warnings. The "spawn" method might be slightly slower, but not by a lot.

I think this just needs a change note and regtest runs.

[kmacdonald-stsci]

Changes look good. In my local testing, this worked for me to avoid the resource warnings. The "spawn" method might be slightly slower, but not by a lot.

I think this just needs a change note and regtest runs.

I added a change fragment and kicked off a regression test here:

https://github.com/spacetelescope/RegressionTests/actions/runs/13726398697