Adds support for LED switches to LED enabled managed UniFi devices and new real-time Trigger system (#66)

- Adds LED control for LED capable UniFi devices
- Adding a new `UnifiLedToggleSwitch` entity.
- Fetching LED states from the `/stat/device` endpoint.
- Allowing users to toggle the LED on/off via a switch entity.
- switch entity has additional meta data, including mac address and model id
- Extends LED toggle to other devices
- Enhance API operation queue with retry logic and device LED control
- Added `QueuedOperation` class for managing queued operations with retries.
- Enhanced `ApiOperationQueue` to include retry logic and queue management.
- Updated LED toggle handling for devices in `switch.py` and `rule.py`.
- Update version in manifest.json from 2.3.0-beta.1 to 2.3.0, promoting the beta release to stable.
- Refactor GitHub Actions workflows by removing the HACS validation from `hacs-integration.yml` and creating a new `hass-validation.yml` for dedicated Home Assistant validation. This improves workflow organization and clarity.
- Implement trigger system for UniFi Network Rules
- Addition of a `triggers.yaml` file defining various triggers for rule events (enabled, disabled, changed, deleted).
- Refactoring of the websocket message handling to integrate with the new trigger system, allowing for more efficient processing of rule-related events.
- Updates to the `coordinator.py` and `trigger.py` files to support the new trigger logic and improve logging for debugging purposes.
- Minor adjustments to the `manifest.json` to include the new trigger platform.
- Enhance UniFi Network Rules integration with real-time trigger system
- Added a new section in `README.md` detailing the real-time triggers, their features, and setup instructions.
- Updated `trigger.py` to support device automation style schemas and improved logging for better debugging.
- Enabled detailed logging for trigger detection and processing, enhancing the ability to monitor rule changes.
- Updated `const.py` to enable trigger logging for state-diff debugging.
- Incremented version in `manifest.json` to 3.0.0 to reflect the significant enhancements.

Author: sirkirby

.github/workflows/hacs-integration.yml

@@ -4,8 +4,6 @@ on:
   workflow_dispatch:
   push:
   pull_request:
-  schedule:
-    - cron: "0 0 * * *"
 
 permissions:
   contents: read
@@ -37,24 +35,3 @@ jobs:
               description: conclusion === 'success' ? 'HACS validation passed!' : 'HACS validation failed.',
               context: 'HACS Validation'
             });
-
-  validate:
-    name: Validate with hassfest
-    runs-on: "ubuntu-latest"
-    steps:
-      - uses: "actions/checkout@v4"
-      - uses: "home-assistant/actions/hassfest@master"
-      - name: Report Hassfest Status
-        if: always()
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const conclusion = '${{ job.status }}'.toLowerCase();
-            await github.rest.repos.createCommitStatus({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              sha: context.sha,
-              state: conclusion === 'success' ? 'success' : 'failure',
-              description: conclusion === 'success' ? 'Hassfest validation passed!' : 'Hassfest validation failed.',
-              context: 'Hassfest Validation'
-            });

.github/workflows/hass-validation.yml

@@ -0,0 +1,34 @@
+name: Home Assistant Validation
+
+on:
+  workflow_dispatch:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+  checks: write
+  pull-requests: write
+  statuses: write
+
+jobs:
+  validate:
+    name: Validate with hassfest
+    runs-on: "ubuntu-latest"
+    steps:
+      - uses: "actions/checkout@v4"
+      - uses: "home-assistant/actions/hassfest@master"
+      - name: Report Hassfest Status
+        if: always()
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const conclusion = '${{ job.status }}'.toLowerCase();
+            await github.rest.repos.createCommitStatus({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              sha: context.sha,
+              state: conclusion === 'success' ? 'success' : 'failure',
+              description: conclusion === 'success' ? 'Hassfest validation passed!' : 'Hassfest validation failed.',
+              context: 'Hassfest Validation'
+            });