Migrate some DEFAULT_FOLDER to keyboard_aliases.hjson

[zvecr]

Description

Migrated keyboard rules.mk which only contain DEFAULT_FOLDER and alias does not yet exist.

Script used

#!/bin/bash

head -n -2 data/mappings/keyboard_aliases.hjson > /tmp/keyboard_aliases.hjson
echo "    }," >> /tmp/keyboard_aliases.hjson
echo "    // DEFAULT_FOLDER removed during 2025 Q1 cycle" >> /tmp/keyboard_aliases.hjson

for rule in $(find keyboards/ -name rules.mk | sort | grep -v keymaps); do
    if [[ $(cat $rule | grep . | grep -Ev "^#.*" | grep -v DEFAULT_FOLDER | wc -l) == 0 ]]; then
        default_folder=$(cat $rule | grep . | grep -Ev "^#.*" | sed 's^DEFAULT_FOLDER[= ]*^^')
        kb_folder=$(echo $rule | sed 's?^keyboards/??' | sed 's^/rules.mk^^')
        # echo "ONLY DF - $rule - $kb_folder - $default_folder"

        if [[ ! -d keyboards/$default_folder ]]; then
            echo "DF no exists"
            continue
        fi
        
        if grep -q '\s"'$kb_folder'"' data/mappings/keyboard_aliases.hjson; then
            echo "dupe:$kb_folder"
            continue
        fi

        # append
        echo -e '    "'$kb_folder'": {\n        "target": "'$default_folder'"\n    },' >> /tmp/keyboard_aliases.hjson
        # remove
        rm -f $rule
    fi
done

# remove last ,
truncate -s-2 /tmp/keyboard_aliases.hjson

echo -e "\n}" >> /tmp/keyboard_aliases.hjson

mv /tmp/keyboard_aliases.hjson data/mappings/keyboard_aliases.hjson

Refactoring remaining use of DEFAULT_FOLDER will follow shortly after what can be automated.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout (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).