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

[Keyboard] Latinpad LED index correction (#17109)

[Keyboard] mach3 LED index correction (#17110)

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

[Keyboard] Add Iron165R2 PCB support (#16948)

[Keyboard] Fix too many elements in g_led_config for quark_lp (#17117)

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

[Keyboard] Fix compilation issues for Quark LP (#17009)

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

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

DigiCarpice Configurator Rendering Fix (#17113)

* info.json: apply friendly formatting

* info.json: rebuild layout data

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

fix tiger80 matrix error (#17107)

Warn about LTO with arm_atsam, not ChibiOS. (#17106)

Various fixes for g_led_config lint warnings (#17104)

Data driven `g_led_config` (#16728)

RESET -> QK_BOOT default keymaps (#17037)

Rename keymap_extras headers for consistency (#16939)

[Feature] Add support for multiple switchs/solenoids to Haptic Feedback engine (#15657)

Check for ongoing transfers on the OUT endpoint (#16974)

...when attempting to start a receiving USB transfer. Previously, we would
check on the IN endpoint which is the transmitting part of the USB endpoint.
This is wrong and lead to two USB transfers being started immediately
after each other in case of e.g. RAW HID endpoints:

1. When finishing an OUT transfer the low level USB driver calls the out_cb
callback, which in turn initiates another OUT transfer by calling
qmkusbDataReceived.

2. When the raw hid receive channel runs empty inside the raw_hid task,
another OUT transfer is started to potentially fill the channel again. This
happens by calling ibnotify.

Both events occur directly after each other, thus triggering the bug.

Format code according to conventions (#17096)