[BUG] Zephyr upstream Button samples requires `zephyr,code` property in DTS

[rexut]

Describe the bug

Since Zephyr v4.4.0 the aliased GPIO button (child node in gpio-keys) must provide a valid INPUT_KEY value in property zephyr,code. The button sample has been converted to use the Input API, see: zephyrproject-rtos/zephyr@68999e6fcf2e3 and zephyrproject-rtos/zephyr#101584

To Reproduce
Steps to reproduce the behavior:

1. setup proper workspace
2. following the direction from Build and Programming in Grove wiring for tests, e.g.:

   west build -b nucleo_f413zh -p \
        --shield "seeed_grove_base_v2 grove_btn_d4 grove_led_d6 grove_pwm_led_d6 x_grove_testbed" \
        -d build/button-nucleo_f413zh-x_grove_testbed zephyr/samples/basic/button
   

3. See error

Expected behavior

Sample can build w/o any compilation.

Impact

Showstopper, because next release v4.5.0 is blocked.

Logs and console output

.../zephyr/include/zephyr/toolchain/gcc.h:87:36:
   error: static assertion failed:
   "zephyr-code must be specified to use the input-gpio-keys driver"

Screenshots
Non.

Development Environment (please complete the following information):

• OS: Linux, Ubuntu 20.04 (LTS)
• Toolchain: Zephyr SDK v1.0.1
• Version: main branch

Additional context
Non.