Use ESPHome watchdog timeout instead of the custom PN532 override

[Copilot]

TagTuner was still routing PN532 through a repository-specific external component to support long NFC operations. This change switches back to ESPHome’s built-in PN532 component and uses the ESP32 platform watchdog timeout where write-capable devices need a larger execution window.

• Remove the custom PN532 source

  • Drop the external_components override from the shared NFC package so all configs use ESPHome’s standard pn532_i2c implementation.

• Widen the ESP32 watchdog for write-capable targets

  • Add esp32.watchdog_timeout: 15s to the ESP32 device configs that expose NFC write/format flows:
    • tagtuner-D1-custom1.yaml
    • tagtuner-XIAO-custom.yaml
    • tagtuner-atom-grove-ble.yaml
    • tagtuner-on-ha-voice-pe.yaml

• Keep tagreader unchanged in behavior

  • Leave the tagreader variant on the standard PN532 component without extra write-related watchdog tuning, since it does not expose NFC write options.

esp32:
  board: wemos_d1_mini32
  watchdog_timeout: 15s
  framework:
    type: esp-idf

• Fixes extend watchdog_timeout instead of using custom pn532 component #72