Use confounds file with non-steady-state columns to identify dummy volumes

[tsalo]

When --dummy-scans is set to auto (the default), XCP-D attempts to infer the right number of dummy volumes from the fMRIPrep confounds file. However, starting in #1255, I connected the output of a node that removes the dummy volume columns from the confounds file to the node that looks for those columns, which resulted in dummy volumes not being flagged and removed by the post-processing workflow. This was identified by a user, Bianca Serio, in https://neurostars.org/t/filenotfounderror-no-bold-data-found-in-allowed-spaces-fslr/30968.

THIS BUG AFFECTS VERSIONS 0.10.0rc1 - 0.10.0

Changes proposed in this pull request

• Use unfiltered confounds file to identify non-steady-state (i.e., dummy) volumes to remove from the BOLD data, rather than the filtered version that only include motion columns.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.96%. Comparing base (0e07ef1) to head (86a27e3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1330   +/-   ##
=======================================
  Coverage   78.96%   78.96%           
=======================================
  Files          59       59           
  Lines        7406     7406           
  Branches      962      962           
=======================================
  Hits         5848     5848           
  Misses       1268     1268           
  Partials      290      290           

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles