Removing RK G68, not compatible with QMK

[Thomaz-Peres]

Description

Removing the RK G68 because it isn't compatible with the QMK. This is confusing many people trying to use the Royal Kludge. Sorry about that

I don't know how the rules to removing something work (I've searched in the docs, but didn't find anything), and this probably doesn't happen often, but following the Thread here, it's okay.

Please let me know if something is wrong

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

[zvecr]

Removing the RK G68 because it isn't compatible with the QMK

If that were the case, how did it get to the point of being added? It would suggest the initial submission had not been tested on hardware.

[Nano204]

I was trying to use QMK with my RKG68 keyboard and it didn't work. So I'm completely agree with this PR, it seems it needs to be rebased @Thomaz-Peres so it can be marge as @drashna already approved it.