chore(deps): update apricote/releaser-pleaser action to v0.6.0 (#507)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
|
[apricote/releaser-pleaser](https://redirect.github.com/apricote/releaser-pleaser)
| action | minor | `v0.5.1` -> `v0.6.0` |

---

### Release Notes

<details>
<summary>apricote/releaser-pleaser (apricote/releaser-pleaser)</summary>

###
[`v0.6.0`](https://redirect.github.com/apricote/releaser-pleaser/blob/HEAD/CHANGELOG.md#v060)

[Compare
Source](https://redirect.github.com/apricote/releaser-pleaser/compare/v0.5.1...v0.6.0)

##### ✨ Highlights

##### Reduced resource usage

`releaser-pleaser` now uses less resources:

- It now skips pushing changes to the release pull request if they are
only a rebase.
- The configurations for GitHub Actions and GitLab CI/CD now makes sure
that only a single job is running at the same time. On GitHub
unnecessary/duplicate jobs are also automatically aborted.
- It handles the stop signals from the CI environment and tries to exit
quickly.

\`\`\`yaml
concurrency:
group: releaser-pleaser
cancel-in-progress: true
\`\`\`

##### Avoid losing manual edits to release pull request

Before, releaser-pleaser was prone to overwriting user changes to the
release pull request if they were made after releaser-pleaser already
started running. There is now an additional check right before
submitting the changes to see if the description changed, and retry if
it did.

##### Proper commit authorship

Before, the release commits were created by `releaser-pleaser &lt;&gt;`.
This was ugly to look at. We now check for details on the API user used
to talk to the forge, and use that users details instead as the commit
author. The committer is still `releaser-pleaser`.

##### Features

- real user as commit author
([#&#8203;187](https://redirect.github.com/apricote/releaser-pleaser/issues/187))
- avoid pushing release branch only for rebasing
([#&#8203;114](https://redirect.github.com/apricote/releaser-pleaser/issues/114))
- colorize log output
([#&#8203;195](https://redirect.github.com/apricote/releaser-pleaser/issues/195))
- graceful shutdown when CI job is cancelled
([#&#8203;196](https://redirect.github.com/apricote/releaser-pleaser/issues/196))
- detect changed pull request description and retry process
([#&#8203;197](https://redirect.github.com/apricote/releaser-pleaser/issues/197))
- run one job concurrently to reduce chance of conflicts
([#&#8203;198](https://redirect.github.com/apricote/releaser-pleaser/issues/198))

##### Bug Fixes

- crash when running in repo without any tags
([#&#8203;190](https://redirect.github.com/apricote/releaser-pleaser/issues/190))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/hetznercloud/hcloud-python).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC41MC4wIiwidXBkYXRlZEluVmVyIjoiNDAuNTAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Author: renovate[bot]

.github/workflows/releaser-pleaser.yml

@@ -17,7 +17,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: releaser-pleaser
-        uses: apricote/releaser-pleaser@v0.5.1
+        uses: apricote/releaser-pleaser@v0.6.0
         with:
           token: ${{ secrets.HCLOUD_BOT_TOKEN }}
           extra-files: |