Miscellaneous keyboard.json migrations

[zvecr]

Description

Problematic keyboards which cannot be automatically migrated. These have been discovered by the following...

for kb in $(qmk list-keyboards); do
    if [[ -f keyboards/${kb}/info.json && -f keyboards/${kb}/rules.mk ]]; then
        true
    elif [[ ! -f keyboards/${kb}/keyboard.json ]]; then
        echo $kb
    fi
done

Common issue seems to be a far less than ideal folder structure, where code is split between a subrevision.

Where specified, DEFAULT_FOLDER has been kept, but now as the only line in a rules.mk.

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