BastardKB: Upstream charybdis/3x5

[burkfers]

Description

This change aims to upstream several changes accumulated in the BastardKB fork.

The most extensive of these changes is dropping support for all controllers and shields other than v2/splinky_3, which has been flattened into the main keyboard. Older variants have not been sold in kits or prebuilts nor been recommended to self-source for a long time.

The dates GH shows on these commits is misleading as some rewriting of the history was necessary to separate commits by keyboard; The functional changes by @0xcharly have been shipping with kits and prebuilts for months and are well-tested. Changes up to and including 3799cd5 are live downstream.

Care has been taken to not lose changes introduced by #23622 and #23627.

Similar changes for all other BastardKB boards are ready, but not yet submitted to reduce the review burden, as they all follow a similar pattern.

Requesting comments.

The full set of related PRs is:

• charybdis/3x5 BastardKB: Upstream charybdis/3x5 #23638
• charybdis/3x6 BastardKB: upstream charybdis/3x6 #23810
• charybdis/4x6 BastardKB: upstream charybdis/4x6 #23811
• skeletyl BastardKB: upstream skeletyl #23812
• tbkmini BastardKB: upstream tbkmini #23813
• scylla BastardBK: upstream scylla #23814
• dilemma/3x5_2 BastardKB: upstream dilemma/3x5_2 #23815
• dilemma/3x5_3 BastardKB: upstream dilemma/3x5_3 #23817
• dilemma/4x6_4 BastardKB: upstream dilemma/4x6_4 #23816
• tbk (removal) BastardKB: remove legacy board tbk #23818

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

[drashna]

Also, just a heads up, you have a number of keyboard.json files removed. These replace info.json+rules.mk (eg, you only need the keyboard.json instead of those). So I/we would prefer if they were not removed, unless there is a specific reason for removing them.

[burkfers]

They have been removed as all revisions of the keyboard have been removed entirely - They have been deprecated for a considerable timeframe; Only the main keyboard, in the state that was previously the revision v2/splinky_3 remains.
The top-level (3x5/-level) info.json was amended with the contents of the only revision that remains supported as the legacy-removal was performed downstream on a master-based state, then the DD conversion was performed, and info.json was renamed to keyboard.json to fit the develop state.

Please let me know if the final result is not to your specifications/expectations.

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[tzarc]

As of August 26, 2024, qmk/qmk_firmware is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control.

As you've submitted a PR containing via or VIA-enabled keymap(s), this is your notice that they should be removed from this PR. You should now submit a secondary PR to the VIA QMK Userspace repository with your associated via or VIA-enabled keymaps instead.

[burkfers]

The BKB team has decided to stop upstreaming efforts at this time.