ci: switch to releaser-pleaser (#1079)

Switch to releaser-pleaser[0] for planning new releases. This adds
the following new features:

- We can easily cut pre-releases, these are always useful if we want to
   allow some customers to test features before making an official release
   or to validate changes made to the release CI workflows.
- We can add our own release notes to each release to better inform
   customers about the new features we added or about any deprecations.

[0] https://github.com/apricote/releaser-pleaser

Author: apricote

.github/release-please-config.json

@@ -1,18 +1,22 @@
-name: Release-please
+name: Releaser-pleaser
 
 on:
   push:
     branches: [main]
+  pull_request_target:
+    types:
+      - edited
+      - labeled
+      - unlabeled
 
 jobs:
-  release-please:
+  releaser-pleaser:
     # Do not run on forks.
     if: github.repository == 'hetznercloud/terraform-provider-hcloud'
 
     runs-on: ubuntu-latest
     steps:
-      - uses: googleapis/release-please-action@v4
+      - name: releaser-pleaser
+        uses: apricote/releaser-pleaser@v0.5.0
         with:
           token: ${{ secrets.HCLOUD_BOT_TOKEN }}
-          config-file: .github/release-please-config.json
-          manifest-file: .github/release-please-manifest.json

.github/release-please-manifest.json

@@ -101,7 +101,7 @@ jobs:
       - uses: codecov/codecov-action@v5
         if: >
           !startsWith(github.head_ref, 'renovate/') &&
-          !startsWith(github.head_ref, 'release-please--')
+          !startsWith(github.head_ref, 'releaser-pleaser--')
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           flags: e2e