DM-40381: Improve mock support and fix bugs in init-input/output handling in QBB

[TallJimbo]

Depends on lsst/daf_butler#879

Checklist

• ran Jenkins
• added a release note for user-visible changes to doc/changes

[codecov]

Codecov Report

Patch coverage: 23.27% and project coverage change: -0.71% ⚠️

Comparison is base (bb42ac7) 84.11% compared to head (fd98449) 83.40%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #368      +/-   ##
==========================================
- Coverage   84.11%   83.40%   -0.71%     
==========================================
  Files          77       77              
  Lines        9082     9173      +91     
  Branches     1740     1579     -161     
==========================================
+ Hits         7639     7651      +12     
- Misses       1158     1232      +74     
- Partials      285      290       +5     

Files Changed	Coverage Δ
...ython/lsst/pipe/base/tests/mocks/_pipeline_task.py	40.77% <9.37%> (-11.52%)	⬇️
python/lsst/pipe/base/graphBuilder.py	60.72% <16.66%> (-0.82%)	⬇️
...ython/lsst/pipe/base/tests/mocks/_storage_class.py	58.47% <47.50%> (-3.23%)	⬇️

... and 3 files with indirect coverage changes

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

[timj]

The barren wasteland that is test coverage on this PR really makes me think that at some point we need to add coverage recording for middleware to ci_middleware so we can get some idea of what our coverage really is.

[TallJimbo]

The barren wasteland that is test coverage on this PR really makes me think that at some point we need to add coverage recording for middleware to ci_middleware so we can get some idea of what our coverage really is.

ci_middleware is already recording all of the coverage it's providing when it's run, but it's a pain to use, because you have to run it locally (and be careful about cleaning up coverage outputs from previous runs) and then do coverage combine and coverage report (or set up editor integration) yourself. Since it doesn't run in GitHub Actions, I think we're stuck with Jenkins as our only option for coverage reporting in a friendlier, more automated way.