ENH: Use data-based padding instead of "odd" padding when filtering in raw.plot

[larsoner]

I was annoyed at the prominent edge ringing when browsing raw data, see rightmost edge of this plot:

I originally decided to combat this by using padtype="constant", but that wasn't quite good enough. I then tried making it so that even for IIR filters we could use our default padtype="reflect_limited", and this helped, but again not quite enough. It also showed that there were slight differences between our "reflect_limited" and NumPy's "reflect", even when there were sufficient samples. Even "reflect" didn't get rid of the ringing entirely, which makes sense for the MEG data I was looking at where very high-frequency, high-amplitude cHPI frequencies cause sharp edges for all of these chosen pad types.

So the ideal/correct fix is really to load sufficient data before and after the viewed window, then filter, then crop back to what you want to display (and do stuff like remove DC from that, choose min/max, decimate, etc.). With that behavior we get something much nicer:

So this PR will need/has following things:

• Clarifies differences between np.pad(..., padtype="reflect") and _smart_pad(..., "reflect_limited") via unit tests. There is really just 1 sample difference, and you could make arguments for either as being more correct. Ours works slightly better for existing tests so let's keep it as-is.
• Removes a (seemingly) unused thread= arg from _process_data
• Removes a +1 that was changed to a +2 in an indexing calculation from ENH: Add time_format to Raw.plot() #9419.
• I need to fully understand why this ☝️ was being done... I think it's probably not the right fix. Instead, somewhere the duration plotted should probably use a np.ceil instead of np.round on the number of samples plotted to ensure that the chosen duration is actually shown. That way when you have start, stop bounds you always get stop - start number of samples, not a kind of weird stop - start + 2, which is the behavior in main. (I think it was still being displayed correctly, but the code for it is unnecessarily complicated).
• I need to update mne-qt-browser to allow _process_data to accept the modified *args and future proof it against stuff like this, and then cut a bugfix release.
• Revert larsoner branch uses in CIs here

I don't think there are too many (any?) tests to add here since it's really hard to quantify the edge ringing. So hopefully just looking

[larsoner]

This is all just unindenting (and maybe 1 or 2 trivial cleanups I think)

[larsoner]

@drammock I think this one is ready for review. If the ideas look reasonable we can review and merge mne-tools/mne-qt-browser#320 first, I can cut a release there, and then revert the larsoner/mne-qt-browser uses here

[drammock]

This is a scheduled Ubuntu 20.04 brownout. Ubuntu 20.04 LTS runner will be removed on 2025-04-15. For more details, see actions/runner-images#11101

[larsoner]

I can open a quick separate PR for that