fix: use proper TLS for Portainer deploys instead of -sk

Switch from -sk (skip cert verification) to -sf (fail on HTTP errors)
now that PORTAINER_URL secrets use Tailscale MagicDNS hostnames with
valid Let's Encrypt certificates.

Author: GeiserX

.github/workflows/deploy-development.yml

@@ -67,7 +67,7 @@ jobs:
           cd /tmp && rm -rf geiserback-deploy
           
           # Trigger Portainer redeploy
-          curl -sk -X PUT \
+          curl -sf -X PUT \
             "${{ secrets.PORTAINER_URL_DEV }}/api/stacks/${{ secrets.PORTAINER_STACK_ID_DEV }}/git/redeploy?endpointId=${{ secrets.PORTAINER_ENDPOINT_ID_DEV }}" \
             -H "X-API-Key: ${{ secrets.PORTAINER_API_KEY_DEV }}" \
             -H "Content-Type: application/json" \

.github/workflows/deploy-production.yml

@@ -72,7 +72,7 @@ jobs:
 
       - name: Trigger Portainer deployment
         run: |
-          curl -sk -X PUT \
+          curl -sf -X PUT \
             "${{ secrets.PORTAINER_URL }}/api/stacks/${{ secrets.PORTAINER_STACK_ID }}/git/redeploy?endpointId=${{ secrets.PORTAINER_ENDPOINT_ID }}" \
             -H "X-API-Key: ${{ secrets.PORTAINER_API_KEY }}" \
             -H "Content-Type: application/json" \