Spring Security Trigger CI from release automation

Currently, a git push from release-next-version.yml does not trigger the CI process (GitHub seems to suppress it to avoid infinite loops). We should update the process to trigger the CI update after updating gradle.properties.

Comment From: eleftherias

This was done by using an explicit GitHub token, rather than the default token in GitHub Actions. See https://github.community/t/push-from-action-does-not-trigger-subsequent-action/16854