Update wiki to include esp32c5 as working with no further bermuda related config needed.

[dflvunoooooo]

I have a esp32c5 from xiao up and running with bermuda for a week now. So the esp32c5 should be included in the wiki as working and no further config needed. The only thing is to get esphome on the c5 one has to use the tasmota flasher, because esphome web does not yet support the c5 (as discussed in the home assistant community and on Derek Seaman's Tech Blog).

There are optional configurations for 5 GHz wifi, but it works without, so the standard config is fine. And I do not know if they are necessary at all. Here is my config

esp32:
  variant: ESP32C5
#  board: esp32-c5-devkitc-1
  flash_size: 8MB
  cpu_frequency: 240MHZ
  framework:
    type: esp-idf
    sdkconfig_options:
     # 5 GHz Wifi suport
      CONFIG_SOC_WIFI_HE_SUPPORT: y
      CONFIG_ESP_WIFI_11AX_SUPPORT: y
      CONFIG_SOC_WIFI_SUPPORT_5G: y
      # Bermuda
      # @grigi found in testing that these options resulted in better responsiveness.
      # BLE 4.2 is supported by ALL ESP32 boards that have bluetooth, the original and derivatives.
      CONFIG_BT_BLE_42_FEATURES_SUPPORTED: y
      # Also enable this on any derivative boards (S2, C3 etc) but not the original ESP32.
#      CONFIG_BT_BLE_50_FEATURES_SUPPORTED: y
      # Extend the watchdog timeout, so the device reboots if the device appears locked up for over 10 seconds.
      CONFIG_ESP_TASK_WDT_TIMEOUT_S: "10"

api:
  encryption:
    key: !secret api_encryption_key
  # Only enable BLE tracking when wifi is up and api is connected. Gives single-core ESP32-C3 devices time to manage wifi and authenticate with api
  on_client_connected:
     - esp32_ble_tracker.start_scan:
        continuous: true
  # Disable BLE tracking when there are no api connections live
  on_client_disconnected:
    if:
      condition:
        not:
          api.connected:
      then:
        - esp32_ble_tracker.stop_scan:

# Bluetooth-Proxy für Bermuda
bluetooth_proxy:

# BLE-Tracker für Bermuda
esp32_ble_tracker:
  scan_parameters:
    continuous: False # Don't auto start BLE scanning, we control it in the `api` block's automation.
    active: True  # send scan-request packets to gather more info, like device name for some devices.
    interval: 320ms  # default 320ms - how long to spend on each advert channel
    window:   300ms  # default 30ms - how long to actually "listen" in each interval. Reduce this if device is unstable.

The c5 and the s3 boards have psram available. I have not tested if it gives any performance benefit to enable this, but it does not hurt and it is working for the s3 and the c5. Simply add this

psram: 
  mode: quad
  speed: 80MHz

Furthermore, the c5 board has a kind of dual core cpu, similar to the c6. The c5 is a bit more powerful, it has a HP core with 240 MHz and an LP core with 48 MHz as stated by seeedstudio.

I wasn't sure how much of this you would like to have in the wiki. I you wish, I could create a PR.