Reject Unsigned Commit push rule rejects commits by project bot user

Summary

Steps to reproduce

1. Enable Rejecting commits that are not signed for the instance

2. Generate Project Bot User & Token

3. Script to do git push using the project token

Example Project

What is the current bug behavior?

$ git push
remote: GitLab: Commit must be signed with a GPG keyTo http://project_3_bot:token_xyz@gitlab.local/demo/project1.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to ‘http://project_3_bot:token_xyz@gitlab.local/demo/project1.git’

What is the expected correct behavior?

Allowing the push to success.

Either the project bot user can add its GPG key or be excluded from the push rule?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Self-Managed omnibus 13.6.3

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes