rename kprepublic bm keyboards to have a standardized naming format

[peepeetee]

renames

bm60rgb => bm60hsrgb
bm60rgb_iso => bm60hsrgb_iso
bm60poker => bm60hsrgb_poker
bm65rgb => bm65hsrgb
bm65iso => bm65hsrgb_iso
bm68rgb => bm68hsrgb
bm80 => bm80hsrgb

As a result, the directory would look like this:

bm16a
bm16s
bm40hsrgb
bm43a
bm43hsrgb
bm60hsrgb
bm60hsrgb_iso
bm60hsrgb_poker
bm65hsrgb
bm65hsrgb_iso
bm80hsrgb
bm980hsrgb(in flight)

The standardized naming format I've came up with is :
Boards with rgb should be called bmxxrgb, boards with hot swap capability should be called bmxxhs, boards with both should be called bmxxhsrgb.

Varients are denoted by adding a _ followed by the varient.
If the board has neither rgb nor hs, then the varient goes directly after bmxx without the _.
Conversely, if it has either rgb or hs, a _ should be used.

Description

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

• KPrepublic updating their boards to have a second version #14964

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

[peepeetee]

@Deadolus @bitstarr @rgoulter

[bitstarr]

please edit the build command in /keyboards/kprepublic/bm43rgb/keymaps/bitstarr/readme.md

[tzarc]

Just a note for other collaborators: this missed the deadline for the Nov'21 breaking changes -- it's preferable that this goes in earlier rather than later, so I'm marking it to be included.

[peepeetee]

please post suggestions to my standardized naming format in the comments, I could really use them

[bitstarr]

i'm fine whith this. it's a good idea to streamline naming. please make sure to edit all readmes too, so nobody gets confused.

[drashna]

This has merge conflicts that needs resolution

[peepeetee]

i'm fine whith this. it's a good idea to streamline naming. please make sure to edit all readmes too, so nobody gets confused.

I am planning to open another pr to fix individual readmes at a later time, after this has been merged, to minimize work lost if I have to rebase

[peepeetee]

This concerns 2 open PRs.
#15001 by @bdtc123: please put your bm60v2_poker inside bm60hsrgb_poker/rev2
#12852 by @umbacos: rename from bm60ec_rgb to bm60hsrgb_ec

[peepeetee]

@mechmerlin @markva @bytesapart

[zvecr]

I am planning to open another pr to fix individual readmes at a later time

Would rather it was done as part of the same PR

[peepeetee]

I am planning to open another pr to fix individual readmes at a later time

Would rather it was done as part of the same PR

I currently have #14784 open, and I am unsure of how I should handle merging this pr with #14784, thus the hesitancy

[drashna]

I am planning to open another pr to fix individual readmes at a later time

Would rather it was done as part of the same PR

I currently have #14784 open, and I am unsure of how I should handle merging this pr with #14784, thus the hesitancy

mostly, just:

git checkout kprepublic_rename
git merge kprepublic_readmes
git commit
git push

[peepeetee]

I am planning to open another pr to fix individual readmes at a later time

Would rather it was done as part of the same PR

Done, thanks for the suggestion