added variations of breeze & default keymap

[peterlvno]

Add a shield definition for the Breeze split keyboard from Afternoon labs.

This is for the standard breeze variant by default, with the arrow cluster present on the right half but not the left. Additional layouts

The definition is based on a stagnant PR by @idan: https://github.com/zmkfirmware/zmk/pull/1125, which based on an abandoned PR by @devries: https://github.com/zmkfirmware/zmk/pull/735

Board/Shield Check-list

• [x] This board/shield is tested working on real hardware
• [x] Definitions follow the general style of other shields/boards upstream (Reference)
• [x] .zmk.yml metadata file added
• [x] Proper Copyright + License headers added to applicable files (Generally, we stick to "The ZMK Contributors" for copyrights to help avoid churn when files get edited)
• [x] General consistent formatting of DeviceTree files
• [x] Keymaps do not use deprecated key defines (Check using the upgrader tool)
• [x] &pro_micro used in favor of &pro_micro_d/a if applicable
• [x] If split, no name added for the right/peripheral half
• [x] Kconfig.defconfig file correctly wraps all configuration in conditional on the shield symbol
• [x] .conf file has optional extra features commented out
• [x] Keyboard/PCB is part of a shipped group buy or is generally available in stock to purchase (OSH/personal projects without general availability should create a zmk-config repo instead)

[netlify[bot]]

👷 Deploy request for zmk pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	365b353b2923c31f82a90ed383d9ec4b0b0f80c0

[djsiroky]

Hi @peterlvno, thanks for picking up the mantle of trying to get Breeze configs merged into ZMK. With the boards being open-sourced, I imagine there's going to be more interest in using ZMK with the Breeze boards. Your addition of the additional layouts (Southern Breeze, Summer Breeze, etc) is especially helpful.

I can't tell if the failing checks for the last two commits are just for lack of a reviewer, or for some other reason, do you feel this PR is ready for re-review and merging?

[devries]

Tagging @devriesp who opened #735