Update Keychron Q4

[adophoxia]

Description

Superseeds #21406, but this will only cover one board from each series update of PRs.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[dunk2k]

for q4/ansi, is there a default of either v1 or v2?

[adophoxia]

for q4/ansi, is there a default of either v1 or v2?

Can you elaborate more on that?

[drashna]

for q4/ansi, is there a default of either v1 or v2?

No need. It uses the parent folder's keymaps, if they exist. As long as the layout macro is correct and supported, it will compile using those higher level keymaps. You can see this in the QMK CI logs, actually.

Also, diff makes it look... wonky.

[drashna]

Could you add an entry to data/mapping/keyboard_aliases.hjson for the name change (since the old name won't compile on the new version)