Move Keyboards & Keymaps into submodule

[ThePreviousOne]

I'm sure this has been brought up before but I can't find the issue.
Keyboards and keymaps are not part of the firmware. Personally I use the commit history to determine if I need to update my local branch or not, but the majority of commits are either new keyboards & keymaps or documentation changes. I won't advocate moving documentation as thats really just extra work with little benefit considering that documentation changes can be important when there is a new feature added, but the same is not true of keyboards or keymaps.

The commit history is the closest thing we have to a change log, which is important in a project this big to keep track of new features.
I realize maintaining an actual change log is extra work and I wouldn't ask anyone to do it, never the less it is important to have one in some form.

[filterpaper]

There are changes proposed in #11269 to support out-of-tree userspace.

[drashna]

This is a topic that comes up frequently enough.

The biggest issue here isn't just moving stuff, it's also infrastructure stuff. There is a lot that needs to be done to be able to move the keyboards and keymaps, without breaking a bunch of stuff.

[ThePreviousOne]

In what way, I cant see how it would be anymore complex than adding a line to the Docs about cloning the submodule 'if desired'.
Sorry if that sounds argumentative, I'm really just curious and trying to understand.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.
// [stale-action-closed]