docs: Update README examples to use v2.1.0

Author: jereze

README.md

@@ -40,7 +40,7 @@ steps:
       fetch-depth: 0
 
   # Deploy your application
-  - uses: 47ng/actions-clever-cloud@v2.0.0
+  - uses: 47ng/actions-clever-cloud@v2.1.0
     env:
       CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}
       CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}
@@ -60,7 +60,7 @@ If you have committed the `.clever.json` file, you only need to specify
 the alias of the application to deploy:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     alias: my-app-alias
   env:
@@ -72,7 +72,7 @@ If you don't have this `.clever.json` file or you want to explicly
 deploy to another application, you can pass its ID:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     appID: app_facade42-cafe-babe-cafe-deadf00dbaad
   env:
@@ -115,7 +115,7 @@ You can set extra environment variables on the deployed application under the
 key=value).
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     setEnv: | # <- note the pipe here..
       FOO=bar
@@ -155,7 +155,7 @@ you can specify a timeout in seconds after which the workflow will move on,
 regardless of the deployment status:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     timeout: 1800 # wait at maximum 30 minutes before moving on
   env:
@@ -170,7 +170,7 @@ regardless of the deployment status:
 Clever Cloud uses a Git remote to perform deploys. By default, if the commit you want to deploy is not a fast-forward from the commit currently deployed, the deploy will be rejected. You can pass `force: true` to force the deploy anyway:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     appID: app_facade42-cafe-babe-cafe-deadf00dbaad
     force: true
@@ -191,7 +191,7 @@ When the local and remote commits are identical, you can control what happens us
 - `rebuild`: Rebuild and redeploy the application
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     sameCommitPolicy: restart
   env:
@@ -206,7 +206,7 @@ When the local and remote commits are identical, you can control what happens us
 You can write the deployment logs to a file for archiving:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     logFile: ./clever-cloud-deploy.log
   env:
@@ -225,7 +225,7 @@ If your deployment process is susceptible to log secrets or PII, you can also
 disable it from printing onto the console, using the `quiet` option:
 
 ```yml
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     quiet: true
   env:
@@ -247,7 +247,7 @@ This action follows [SemVer](https://semver.org/).
 
 To specify the version of the action to use:
 
-- `uses: 47ng/actions-clever-cloud@v2.0.0`: latest stable version
+- `uses: 47ng/actions-clever-cloud@v2.1.0`: latest stable version
 - `uses: 47ng/actions-clever-cloud@3e5402496b8d6492401ebb3134acfeccc25c3fce`: pinned to a specific Git SHA-1 (check out the [releases](https://github.com/47ng/actions-clever-cloud/releases))
 - `uses: docker://ghcr.io/47ng/actions-clever-cloud:latest`: latest code from master (not recommended, as it may break: hic sunt dracones.)
 
@@ -291,12 +291,12 @@ Using this action at work ? [Sponsor me](https://github.com/sponsors/franky47) t
 
 ```yml
 # This will NOT deploy only the build folder:
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     working-directory: ./build # ❌ Only changes where the action runs
 
 # This will deploy only the build folder:
-- uses: 47ng/actions-clever-cloud@v2.0.0
+- uses: 47ng/actions-clever-cloud@v2.1.0
   with:
     deployPath: ./build # ✅ Only sends these files to Clever Cloud
 ```