[Keyboard] Add Arrow Mechanics WINGS

[arrowmechanics]

Description

Add base support for Arrow Mechanics WINGS keyboard with all the essential features

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).

[arrowmechanics]

applied review suggestions, please see one comment

[arrowmechanics]

applied all review suggestions

[arrowmechanics]

No more functional changes in this PR! (just fixes if needed)

[zvecr]

All the constant merging is doing is burning CI minutes and making other PRs workflow runs take longer.

[arrowmechanics]

I see, I'll stop and wait until You're ready :)

[arrowmechanics]

Is there anything else that stops us from merging?

[arrowmechanics]

All the constant merging is doing is burning CI minutes and making other PRs workflow runs take longer.

Also, this might be a thing for thought when it comes to maintenance rules of the QMK repo - how should I know as a minor contributor, how many updates to the main branch should I expect before my PR is taken care of?

I understand my mistake now, but it's not that obvious in general for there are no releases, no time-related or anyhow strict rules of merging to main. It actually looks confusing as multiple minor updates were merged in the meantime without even passing the pipelines - maybe it's a good idea to elaborate on that in the docs?
Or maybe I shouldnt be allowed to be so over-eager with triggering the CI? Isn't there a maintainer-validation mechanism?

[tzarc]

It's not obvious, because the vast majority of people aren't so eager to update their repo.
I run QMK CI locally, so I pay for electricity costs associated with it -- normal use I'm okay with.

I've disabled CI for your PR for now. If/when collabs get back to it, they can remove the label and retrigger CI on demand.

[arrowmechanics]

It's not obvious, because the vast majority of people aren't so eager to update their repo. I run QMK CI locally, so I pay for electricity costs associated with it -- normal use I'm okay with.

I've disabled CI for your PR for now. If/when collabs get back to it, they can remove the label and retrigger CI on demand.

I really am keen, we're yet another start-up that took up QMK as a key element. Still I didn't know You run it locally.
This makes me think it might be good time to start doing this:

I promise to go for more as soon as we're profitable :P

[arrowmechanics]

This PR seems to have too many comments/issues vs. few changes that it actually introduces. Closing to create a clean version since it may take too much time to dig into things that are already fixed.