docs(S4PL-00416EU): rewrite "Noisy status updates" with concrete debounce recipe

[coyotte508]

docs(S4PL-00416EU): rewrite "Noisy status updates" with a concrete debounce recipe

Disclosure: the wording and this PR description were drafted by an AI coding assistant under my direction. The before/after numbers below were measured live on my Shelly Power Strip 4 Gen4.

The existing note on the S4PL-00416EU device page acknowledged the device's frequent reporting but only linked to a third-party HASS write-up without telling users what to do. This PR replaces it with a copy-pasteable configuration.yaml snippet that uses Zigbee2MQTT's built-in debounce / debounce_ignore options:

devices:
  '0xYYYYYYYYYYYYYYYY':
    friendly_name: My Power Strip
    debounce: 5
    debounce_ignore:
      - state_1
      - state_2
      - state_3
      - state_4
      - action

debounce_ignore is the important part: it makes sure switch state changes (and external button-press actions) flush the debounce buffer immediately, so user-visible behavior stays snappy.

Verified on a real device

Shelly Power Strip 4 Gen4 (S4PL-00416EU) on the Zigbee firmware, zhc 26.12.0 / z2m 2.x:

• Without debounce: ~30 publishes / 30 s on the device topic.
• With debounce: 5 and state_* in debounce_ignore: ~5 publishes / 30 s.
• Switch state changes still propagate immediately (~200 ms after device acknowledgement, vs. up to +5 s if state_* weren't ignored).

Refs Koenkk/zigbee2mqtt#30544, Shelly community thread.

[coyotte508]

Closing this — most users probably don't touch configuration.yaml directly, and adjusting the per-attribute reporting thresholds from the device page in the Z2M web UI is a less wordy / more discoverable workaround than a yaml snippet. The existing note already links to the community write-up that explains the UI steps, which is enough.