Merge remote-tracking branch 'origin/master' into develop

[Keyboard] Add WTF60 (#12883)

[Keyboard] New Keyboard - Murphpad (#12885)

Co-authored-by: Ryan <fauxpark@gmail.com>

Merge remote-tracking branch 'origin/master' into develop

[Keyboard] Add support for alfredslab 65 (#12334)

Co-authored-by: Ryan <fauxpark@gmail.com>

Add support for up to 4 IS31FL3733 drivers (#12342)

Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com>

Merge remote-tracking branch 'origin/master' into develop

[Keymap] Add kanbara's planck/rev4 keymap (#12486)

Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Jay Morrow <jay.morrow@apple.com>

Merge remote-tracking branch 'origin/master' into develop

[Keyboard] Add 75 Pixels Ortholinear Keyboard (#12220)

Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Sendy Aditya Suryana <sendy.suryana@go-jek.com>

ensure we do not conflict with existing keymap aliases (#12976)

Merge remote-tracking branch 'origin/master' into develop

fix example code in docs/feature_rgblight.md (#12960)

Merge remote-tracking branch 'origin/master' into develop

Add EE_HANDS documentation command example (#12730)

* Add command example

* Remove c tag

Co-authored-by: filterpaper <filterpaper@localhost>

Merge remote-tracking branch 'origin/master' into develop

Resolved Conflicts:
	lib/python/qmk/tests/test_cli_commands.py
	util/install/fedora.sh

Align our subprocess usage with current best practices. (#12940)

* Align our subprocess usage with current best practices.

* remove unused import

* Apply suggestions from code review

Co-authored-by: Ryan <fauxpark@gmail.com>

* fix the cpp invocation for older python

* allow for unprompted installation

* make sure qmk new-keyboard works on windows

Co-authored-by: Ryan <fauxpark@gmail.com>

matrix: wait for row signal to go HIGH for every row (#12945)

I noticed this discrepancy (last row of the matrix treated differently than the
others) when optimizing the input latency of my keyboard controller, see also
https://michael.stapelberg.ch/posts/2021-05-08-keyboard-input-latency-qmk-kinesis/

Before this commit, when tuning the delays I noticed ghost key presses when
pressing the F2 key, which is on the last row of the keyboard matrix: the
dead_grave key, which is on the first row of the keyboard matrix, would be
incorrectly detected as pressed.

After this commit, all keyboard matrix rows are interpreted correctly.

I suspect that my setup is more susceptible to this nuance than others because I
use GPIO_INPUT_PIN_DELAY=0 and hence don’t have another delay that might mask
the problem.

Merge remote-tracking branch 'origin/master' into develop

revert error introduced in PR #12871 (#12891)