[ENH] Add optional low_cutoff and high_cutoff columns for fnirs channels.tsv

[Remi-Gau]

• relates to low_cutoff and high_cutoff columns in fnirs_tapping bids-examples#396

makes it consistent with what is done in EEG, iEEG, MEG

See the HTML table here

@rob-luke @lpollonini does this make sense to you

Closes bids-standard/bids-examples#396.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (48a61a6) 87.83% compared to head (c612a1b) 87.83%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1597   +/-   ##
=======================================
  Coverage   87.83%   87.83%           
=======================================
  Files          16       16           
  Lines        1356     1356           
=======================================
  Hits         1191     1191           
  Misses        165      165           

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

[effigies]

Seems obviously right, given that examples submitted by the BEP leads include them, and there is a clear interpretation. Adding these will not invalidate or increase validator noise on any datasets, so I vote for merge after the usual 5 days, regardless of whether we hear back.

[Remi-Gau]

Seems obviously right, given that examples submitted by the BEP leads include them, and there is a clear interpretation. Adding these will not invalidate or increase validator noise on any datasets, so I vote for merge after the usual 5 days, regardless of whether we hear back.

good with me

[tsalo]

Makes sense to me.

[lpollonini]

Makes total sense. Approved!

[effigies]

Going to invoke rule 5 and merge now, as it will eliminate a spurious validator error.