[Feature request] Add names to keycodes in Vial

[ModelFKeyboard]

Can some unlabelled scancodes like 0x7C02 instead have a real name in Vial, like all the other keys? Users report that it is frustrating to have to research certain key names in the documentation while almost all keys have easy to understand names.

[ploxiln]

I think generally yes, Vial does generally do this, but it seems to be missing some of the ones used by default by these "Brand New Model F Keyboards" (and Beamsprings). The ones I notice are DEBUG and EEPROM_RESET

The xwhatsit/wcass firmware for my Model F is forked from older Vial 0.4.x source, which has these defined in quantum_keycodes.h (and used in the .c default keymap defs for these keyboards):

    // Loose keycodes - to be used directly
    RESET = 0x5C00,
    DEBUG,  // 5C01

...

    MI_VEL_0,  // 5C92
#ifdef VIA_ENABLE
    MI_VEL_1 = MI_VEL_0,
#else
    MI_VEL_1,  // 5C93
#endif
    MI_VEL_2,   // 5C94
    MI_VEL_3,   // 5C95
...

    // Clear EEPROM
    EEPROM_RESET,  // 5CDF

I'm not sure what's up with MI_VEL_1 but that explains why EEPROM_RESET comment is off-by-one from the actual keycode used on my keyboard.

... this may be because resetting eeprom made more sense with plain QMK, not so much with Vial? and "debug" doesn't do much because there isn't room for debug logging in the firmware builds for these atmega32u2? so maybe these keys don't really do anything?

Anyway, for the newer leyden-jar board and firmware, I guess it's different "special keycodes" that seem to be missing from the Vial GUI translation tables ...

[ploxiln]

This PR appears related to the ones I noticed: https://github.com/vial-kb/vial-gui/pull/327/files

(... but EEPROM_RESET is off-by-one from my keyboard firmware based on vial 0.4 ...)

[ploxiln]

btw 0x7C02 in the newer "leyden_jar" firmware is the newer DEBUG after the big keycode remapping of 2022

quantum/keycodes.h
696:    QK_DEBUG_TOGGLE = 0x7C02,