Enabled php 8.1 in testsuite, simplified githb workflows

.github/workflows/automatino-pr-description-validate.yml

@@ -0,0 +1,11 @@
+name: "Automation - PR Description Validate"
+
+on:
+  pull_request:
+    types: ["opened", "edited", "reopened", "ready_for_review"]
+
+jobs:
+  automation:
+    uses: aeon-php/actions/.github/workflows/automation-pr-description-validate.yml@main
+    secrets:
+      automation_github_token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/automation-changelog-release.yml

@@ -0,0 +1,12 @@
+name: "Automation - Changelog Release"
+
+on:
+  push:
+    tags:
+      - '*'
+
+jobs:
+  automation:
+    uses: aeon-php/actions/.github/workflows/automation-changelog-release.yml@main
+    secrets:
+      automation_github_token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/automation-changelog-update.yml

@@ -0,0 +1,12 @@
+name: "Automation - Changelog Update"
+
+on:
+  push:
+    branches:
+      - "3.x"
+
+jobs:
+  automation:
+    uses: aeon-php/actions/.github/workflows/automation-changelog-update.yml@main
+    secrets:
+      automation_github_token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/automation-release-description-update.yml

@@ -0,0 +1,12 @@
+name: "Automation - Release Description Update"
+
+on:
+  release:
+    types:
+      - "created"
+
+jobs:
+  automation:
+    uses: aeon-php/actions/.github/workflows/automation-release-description-update.yml@main
+    secrets:
+      automation_github_token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/dependabot-auto-merge.yaml

@@ -0,0 +1,31 @@
+name: "Dependabot Auto Merge"
+
+on:
+  workflow_run:
+    types:
+      - "completed"
+    workflows:
+      - 'Test Suite'
+
+jobs:
+  merge-me:
+    name: Merge me!
+    runs-on: ubuntu-latest
+    steps:
+      - # It is often a desired behavior to merge only when a workflow execution
+        # succeeds. This can be changed as needed.
+        if: ${{ github.event.workflow_run.conclusion == 'success' }}
+        name: Merge me!
+        uses: ridedott/merge-me-action@v2
+        with:
+          # Depending on branch protection rules, a  manually populated
+          # `GITHUB_TOKEN_WORKAROUND` secret with permissions to push to
+          # a protected branch must be used. This secret can have an arbitrary
+          # name, as an example, this repository uses `DOTTBOTT_TOKEN`.
+          #
+          # When using a custom token, it is recommended to leave the following
+          # comment for other developers to be aware of the reasoning behind it:
+          #
+          # This must be used as GitHub Actions token does not support pushing
+          # to protected branches.
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}