NO-ISSUE feat: upgrade version to 0.1.1

### Description

- As the title.

### Package Changes

_No response_

### Screenshots

_No response_

### Reference

- Resolves #36
- Solution: https://stackoverflow.com/questions/75131872/error-failed-to-solve-failed-commit-on-ref-unexpected-status-400-bad-reques
- Docker document: https://docs.docker.com/build/ci/github-actions/attestations/#max-level-provenance
  > Note that adding attestations to an image means you must push the image to a registry directly, as opposed to loading the image to the local image store of the runner. This is because the local image store doesn't support loading images with attestations.

### Checklist

- [x] A milestone is set
- [x] The related issuse has been linked to this branch

Reviewed-on: #38
Reviewed-by: zoe <zoe@noreply.localhost>
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>

.gitea/workflows/deployment.yaml

@@ -17,7 +17,7 @@ jobs:
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
 
-      - name: Build image and push to registry
+      - name: Login to registry
         uses: docker/login-action@v3
         with:
           registry: ${{ vars.REGISTRY }}
@@ -28,6 +28,7 @@ jobs:
         uses: docker/build-push-action@v6
         with:
           push: true
+          provenance: false
           context: ./frontend
           tags: |
             ${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:latest