fix: sort manifest.json keys per hassfest requirements

Keys must be: domain, name, then alphabetical. Previous order had
dependencies, integration_type, requirements after version which
fails hassfest validation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: chrisdpurcell

custom_components/ha_light_controller/manifest.json

@@ -3,11 +3,11 @@
   "name": "Light Controller",
   "codeowners": ["@L3DigitalNet"],
   "config_flow": true,
+  "dependencies": ["light", "group"],
   "documentation": "https://github.com/L3DigitalNet/HA-Light-Controller",
+  "integration_type": "service",
   "iot_class": "calculated",
   "issue_tracker": "https://github.com/L3DigitalNet/HA-Light-Controller/issues",
-  "version": "0.3.0",
-  "integration_type": "service",
   "requirements": [],
-  "dependencies": ["light", "group"]
+  "version": "0.3.0"
 }