Remove Arduino-specific BLE limitations from documentation

Author: bdraco

content/components/bluetooth_proxy.md

@@ -51,10 +51,9 @@ bluetooth_proxy:
 ```
 
 - **active** (*Optional*, boolean): Enables proxying active connections. Defaults to `true`.
-- **cache_services** (*Optional*, boolean): Enables caching GATT services in NVS flash storage which significantly speeds up active connections. Defaults to `true` when using the ESP-IDF framework.
+- **cache_services** (*Optional*, boolean): Enables caching GATT services in NVS flash storage which significantly speeds up active connections. Defaults to `true`.
 - **connection_slots** (*Optional*, int): The maximum number of BLE connection slots to use.
-  Each configured slot consumes ~1KB of RAM. This can only be adjusted when using
-  the `esp-idf` framework up to a maximum of `9`. It is recommended not to exceed `5`
+  Each configured slot consumes ~1KB of RAM, with a maximum of `9`. It is recommended not to exceed `5`
   connection slots to avoid memory issues. Defaults to `3`.
   The value must not exceed the total configured `max_connections`
   for {{< docref "esp32_ble_tracker/" >}}.

content/components/esp32_ble.md

@@ -54,7 +54,7 @@ The `disable_bt_logs` option intelligently disables only the Bluetooth logging c
 
 {{< /note >}}
 
-- **connection_timeout** (*Optional*, [Time](#config-time)): The maximum time to wait for a BLE connection to be established. Only available when using ESP-IDF framework. Defaults to `20s`.
+- **connection_timeout** (*Optional*, [Time](#config-time)): The maximum time to wait for a BLE connection to be established. Defaults to `20s`.
 
   - Range: 10 to 180 seconds
   - This timeout should align with the timeout used by your BLE client software to prevent connection slot waste
@@ -72,7 +72,7 @@ The `advertising` option is an advanced feature that manually enables BLE advert
 {{< /note >}}
 
 - **advertising_cycle_time** (*Optional*, [Time](#config-time)): The time interval for cycling through multiple advertisements. Only applicable when advertising is enabled. Defaults to `10s`.
-- **max_notifications** (*Optional*, integer): The maximum number of BLE characteristics that can have notifications enabled across all connections. Only available when using ESP-IDF framework. Defaults to `12`.
+- **max_notifications** (*Optional*, integer): The maximum number of BLE characteristics that can have notifications enabled across all connections. Defaults to `12`.
 
   - Range: 1 to 64
   - This is a global limit shared across all BLE connections

content/components/esp32_ble_tracker.md

@@ -99,8 +99,7 @@ you can use OTA updates again.
 - **id** (*Optional*, [ID](#config-id)): Manually specify the ID for this ESP32 BLE Hub.
 - **max_connections** (*Optional*, int): The maximum number of BLE connection slots to use.
   Each configured slot consumes ~1KB of RAM. It is recommended not to exceed `5`
-  connection slots to avoid memory issues. Defaults to `3`.
-  This can only be adjusted when using the `esp-idf` framework up to a maximum of `9`.
+  connection slots to avoid memory issues. Defaults to `3`, with a maximum of `9`.
   This value cannot exceed the total number of `connection_slots` for the
   {{< docref "bluetooth_proxy/" >}} component combined with the total
   configured {{< docref "ble_client/" >}} instances.