feat: Add GitHub Actions workflows for Docker build, publish, documentation deployment, and quality checks

- Implemented `docker-build.yml` for building and pushing Docker images with multi-platform support, Trivy security scanning, and conditional builds based on commit messages.
- Created `docker-publish.yml` for streamlined Docker image publishing with Trivy vulnerability scanning on push events.
- Added `docs.yml` to automate documentation deployment to GitHub Pages, including a custom HTML structure and markdown conversion.
- Introduced `propagate-changes.yml` to automate PR creation for synchronizing changes between main, development, and feature branches.
- Established `quality-checks.yml` for running backend (Go) and frontend (React) quality checks, including tests and linting.
- Developed `release.yml` for generating changelogs and creating GitHub releases upon version tag pushes.
- Set up `renovate.yml` for automated dependency updates on a daily schedule.

.github/ISSUE_TEMPLATE/alpha-feature.yml

@@ -0,0 +1,93 @@
+name: 🏗️ Alpha Feature
+description: Create an issue for an Alpha milestone feature
+title: "[ALPHA] "
+labels: ["alpha", "feature"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Alpha Milestone Feature
+        Features that are part of the core foundation and initial release.
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How critical is this feature?
+      options:
+        - Critical (Blocking, must-have)
+        - High (Important, should have)
+        - Medium (Nice to have)
+        - Low (Future enhancement)
+    validations:
+      required: true
+
+  - type: input
+    id: issue_number
+    attributes:
+      label: Planning Issue Number
+      description: Reference number from PROJECT_PLANNING.md (e.g., Issue #5)
+      placeholder: "Issue #"
+    validations:
+      required: false
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature Description
+      description: What should this feature do?
+      placeholder: Describe the feature in detail
+    validations:
+      required: true
+
+  - type: textarea
+    id: tasks
+    attributes:
+      label: Implementation Tasks
+      description: List of tasks to complete this feature
+      placeholder: |
+        - [ ] Task 1
+        - [ ] Task 2
+        - [ ] Task 3
+      value: |
+        - [ ]
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance Criteria
+      description: How do we know this feature is complete?
+      placeholder: |
+        - [ ] Criteria 1
+        - [ ] Criteria 2
+      value: |
+        - [ ]
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: categories
+    attributes:
+      label: Categories
+      description: Select all that apply
+      options:
+        - label: Backend
+        - label: Frontend
+        - label: Database
+        - label: Caddy Integration
+        - label: Security
+        - label: SSL/TLS
+        - label: UI/UX
+        - label: Deployment
+        - label: Documentation
+
+  - type: textarea
+    id: technical_notes
+    attributes:
+      label: Technical Notes
+      description: Any technical considerations or dependencies?
+      placeholder: Libraries, APIs, or other issues that need to be completed first
+    validations:
+      required: false