feat: implement automatic version incrementing with CI/CD strategy

- Add Gitea Actions workflow for automatic version bumping
- Update test workflow to run linting and tests
- Configure Drone to build images with version tags
- Separate concerns: Gitea Actions for versioning, Drone for Docker builds
- Version format: MAJOR.MINOR.PATCH (auto-increment patch)
- Add comprehensive CI/CD strategy documentation

This prevents race conditions between Gitea Actions and Drone CI by:
1. Gitea Actions handles version bump and creates git tag
2. Tag creation triggers Drone to build Docker images
3. Both systems work sequentially, not in parallel

🤖 Generated with [Claude Code](https://claude.ai/code)

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

.drone.yml

@@ -11,9 +11,12 @@ steps:
       tags: 
         - latest
         - ${DRONE_COMMIT_SHA:0:8}
+        - ${DRONE_BRANCH}-latest
       dockerfile: backend/Dockerfile
       context: backend/
       registry: registry.local.nothaft.cloud
+      build_args:
+        - VERSION=${DRONE_TAG:-dev}
       
   # Build Frontend Docker Image
   - name: build-frontend
@@ -23,9 +26,13 @@ steps:
       tags: 
         - latest
         - ${DRONE_COMMIT_SHA:0:8}
+        - ${DRONE_BRANCH}-latest
       dockerfile: frontend/Dockerfile
       context: frontend/
       registry: registry.local.nothaft.cloud
+      build_args:
+        - VERSION=${DRONE_TAG:-dev}
+        - VITE_API_URL=${VITE_API_URL:-/api}
 
 trigger:
   branch: