Add --force to the release pushes performed by the CI

If the `deploy` step fails, the Github Actions run will be two commits
behind the tip of the branch. We must allow the workflow to remove the
last two (automatic) commits from the branch.

Repos should use a `concurrency` setting to prevent Github Actions from
removing manually added commits.

.github/workflows/deploy-release-reusable.yaml

@@ -111,7 +111,7 @@ jobs:
             git config user.name "ASF Logging Services RM"
             git config user.email private@logging.apache.org
             git commit -S pom.xml -m "Set version to \`$PROJECT_VERSION\`"
-            git push origin
+            git push -f origin
           fi
 
       - name: Release changelog
@@ -128,7 +128,7 @@ jobs:
             git config user.name "ASF Logging Services RM"
             git config user.email private@logging.apache.org
             git commit -S src -m "Release changelog for version \`$PROJECT_VERSION\`"
-            git push origin
+            git push -f origin
           fi
 
       - name: Build the website