west: bump Zephyr main to 3e7672a71bd

- retire 0018 (upstream 67151dfaf73 locks the shared multi-heap) and the
  hal_espressif PSRAM-realloc backport (in the new hal pin)
- 0001: add LR1110/LR2021 to LORA_MODULE_BACKEND_NATIVE's depends on;
  upstream 1263266b615 gated it on its own radios and LR boards silently
  fell to loramac-node
- ble: build the persisted gatt_peer settings key ourselves in the old
  format; bt_addr_le_to_str() changed to "P:AA:.." and would have orphaned
  every key and sent every bonded phone a Service Changed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/adr/0009-wifi-companion-boards.md

@@ -12,8 +12,9 @@ declare it (Heltec V3 and Wireless Tracker at 140/130 contacts, both C6 boards a
 also gets bounded WiFi buffers and a measured 72 KB heap (Kconfig, `HEAP_MEM_POOL_IGNORE_MIN`). Tracker V2, C3
 and the classic ESP32 boards do not fit WiFi + BLE (DRAM). Upstream's
 `set/get wifi.ssid|pwd|enabled`, `set wifi.clear`, `get wifi.status|ip`; applied on reboot; TCP port
-`CONFIG_ZEPHCORE_TCP_PORT` (5000, as upstream). The Zephyr ESP32 WiFi stack needs patches `0017`/`0018` and
-hal_espressif `0001` to survive traffic bursts (§13).
+`CONFIG_ZEPHCORE_TCP_PORT` (5000, as upstream). The Zephyr ESP32 WiFi stack needed patches `0017`/`0018` and
+hal_espressif `0001` to survive traffic bursts; since the 2026-09-26 Zephyr bump only `0017` remains (the other
+two fixes are upstream, `67151dfaf73` and hal_espressif `af97fb02df`) (§13).
 
 ## Decision
 
@@ -21,4 +22,4 @@ WiFi + BLE on every board that can hold both; fewer contacts on the no-PSRAM one
 
 ## Consequences
 
-Watch patches `0017`/`0018` and hal_espressif `0001` on every west update.
+Watch patch `0017` on every west update: upstream's RX path still blocks for 100 ms.