Fix 'Commit and push version increment' step in Azure DevOps

[eduherminio]

Despite ending up green, git push fails apparently due to status checks.
Tag is pushed correctly, though.
Only known workaround used in AoCHelper is disabling the Required status checks step in repo's configuration.

How about giving admin:repo_hook permissions to that Api Key?

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   Examples/FileParserExample/FileParserExample.csproj
	modified:   NugetTest/NugetTest/NugetTest.csproj
	modified:   src/FileParser/FileParser.csproj

no changes added to commit (use "git add" and/or "git commit -a")
[master 7b94a97] Release v1.4.3
 3 files changed, 3 insertions(+), 3 deletions(-)
remote: error: GH006: Protected branch update failed for refs/heads/master.        
remote: error: 8 of 8 required status checks are expected.        
To https://github.com/eduherminio/FileParser
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/eduherminio/FileParser'
To https://github.com/eduherminio/FileParser
 * [new tag]         v1.4.3 -> v1.4.3
Finishing: Commit and push version increment

[eduherminio]

Release pipeline has been moved to GitHub Actions.
Required status check are kept disabled for now, though.