feat: add wifi bluetooth automation trigger

[thomasborgogno]

Summary

Adds two new automation trigger types: Bluetooth device connected/disconnected and Wi-Fi network connected/disconnected. Users can now build automations that fire an action when the phone connects to (or disconnects from) a specific paired Bluetooth device or a specific Wi-Fi network — the same way existing triggers like Charger Connected or Schedule work today.

What's new

• Trigger.kt: 4 new sealed subtypes — BluetoothConnected/BluetoothDisconnected (device address + name) and WifiConnected/WifiDisconnected (SSID), all configurable via a settings sheet like Trigger.Schedule.
• BluetoothModule (new): dynamic BroadcastReceiver on ACTION_ACL_CONNECTED/ACTION_ACL_DISCONNECTED, filtered by MAC address.
• WifiModule (new): ConnectivityManager.NetworkCallback on the Wi-Fi transport, resolving the active SSID via WifiManager and firing on connect/lost.
• AutomationManager: wires both modules into the existing module lifecycle (same pattern as Power/Display/Time modules).
• Editor UI: two new trigger entries in AutomationEditorActivity, each configurable through a bottom sheet:
  • BluetoothDeviceSelectionSheet — pick from the phone's paired devices (requests BLUETOOTH_CONNECT on Android 12+).
  • WifiNetworkSelectionSheet — if the app has Shizuku (or root) authorized, it runs cmd wifi list-networks under shell privileges and lets the user pick straight from the device's saved networks; otherwise it falls back to manual SSID entry with a "Use Current Network" helper (requests ACCESS_FINE_LOCATION, needed by Android to read the current SSID).
• Manifest: added ACCESS_WIFI_STATE (the Bluetooth/location permissions needed were already present).

Why

Requested enhancement to make automations react to connectivity context (e.g. "turn on Wi-Fi calling when connected to home network", "mute when a specific headset disconnects") without needing a schedule or manual toggle.

Test plan

• Create a Trigger automation on "Bluetooth Device Connected"/"Disconnected" for a paired device and verify the linked action fires on connect/disconnect.
• Create a Trigger automation on "Wi-Fi Network Connected"/"Disconnected".
• Verify triggers still fire correctly after the app/service is killed and restarted (foreground service reattachment).