Honor datalad.runtime.use-patool if set regardless of OS (was Windows only)

[mih]

Previously, windows was a declared special case in which the flag was
effectively ignored. This is confusing, and may be unjustified even.

Fixes #5044

[codecov]

Codecov Report

Merging #6033 (68c086d) into maint (53183e3) will decrease coverage by 2.92%.
The diff coverage is 100.00%.

❗ Current head 68c086d differs from pull request most recent head 9cf12ed. Consider uploading reports for the commit 9cf12ed to get more accurate results

@@            Coverage Diff             @@
##            maint    #6033      +/-   ##
==========================================
- Coverage   90.19%   87.26%   -2.93%     
==========================================
  Files         315      312       -3     
  Lines       42165    41037    -1128     
==========================================
- Hits        38030    35812    -2218     
- Misses       4135     5225    +1090     

Impacted Files	Coverage Δ
datalad/support/archives.py	86.06% <100.00%> (-0.28%)	⬇️
datalad/tests/test_installed.py	89.47% <100.00%> (+0.58%)	⬆️
datalad/plugin/wtf.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/addurls.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/no_annex.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/add_readme.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/check_dates.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/support/tests/utils.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/export_archive.py	0.00% <0.00%> (-100.00%)	⬇️
datalad/plugin/export_to_figshare.py	0.00% <0.00%> (-100.00%)	⬇️
... and 201 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53183e3...9cf12ed. Read the comment docs.

[yarikoptic]

and let's push a release with this simple one, we are already at 0.15.1-33-gba32ae216

[yarikoptic]

hm, I do not see github actions for release to ever trigger after merging this PR: https://github.com/datalad/datalad/actions/workflows/release.yml so it was not released. @jwodder -- any clue on what have might happened?
meanwhile I guess I will remove release label from this PR and we could apply it to some other PR to see if release action would finally kick in

[jwodder]

@yarikoptic GitHub Actions was having some problems yesterday; I experienced a run for datalad/git-annex that waited forever and never started.

[yarikoptic]

ah, odd ... I was told that yesterday for some reason many services (not just github) were experiencing issues. I wonder what was the "Common denominator" ;) cool, so let's just try with some other PR merge to maint.