Remove Trivy workflows + Fix YAML syntax errors

Trivy Removal:
- Remove entire docker-security-scan job from security workflow
- Remove Trivy vulnerability scanner from release workflow
- Remove Trivy filesystem scan and related steps
- Update security summary to reflect Trivy removal
- Eliminates GitHub API authentication issues

 YAML Syntax Fixes:
- Fix indentation errors in ci.yml (line 31)
- Fix indentation errors in docs.yml (line 30)
- Correct 'with:' block alignment with 'uses:' statements
- Fix token parameter indentation (8 spaces standard)
- Applied across all workflow files consistently

 Result:
- All workflows now have valid YAML syntax
- No more Trivy-related GitHub API calls
- Cleaner, simpler security workflow
- Workflows ready for successful execution

.gitea/workflows/release.yml

@@ -161,21 +161,7 @@ jobs:
       with:
         token: ${{ secrets.CI_BOT_TOKEN }}
       
-    - name: Run Trivy vulnerability scanner
-      uses: aquasecurity/trivy-action@master
-      with:
-        image-ref: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ needs.create-release.outputs.version }}
-        format: 'sarif'
-        output: 'trivy-results.sarif'
-        github-token: ${{ secrets.GH_TOKEN }}
-      env:
-        GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
-        
-    - name: Upload Trivy scan results
-      uses: actions/upload-artifact@v3
-      with:
-        name: security-scan-results
-        path: trivy-results.sarif
+
 
   # Deploy release to production
   deploy-release: