Add support for GitOps comments on Push commits

[chmouel]

Add supports for GitOps comments on Push commits when using the Git Provider.

Moved the RunPush function to use scm.PushFiles (which use the git binary instead of api) to push files like we do on gitea, since pushing to main via go-github was too painful..

Jira: https://issues.redhat.com/browse/SRVKP-4179

Changes

Submitter Checklist

• 📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).

• ♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.

• ✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).

• 📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.

• 🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.

• 🎁 If feasible, please check if an end-to-end test can be added. See README for more details.

• 🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.74%. Comparing base (b1ea0c2) to head (1d58c04).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1638      +/-   ##
==========================================
- Coverage   65.74%   65.74%   -0.01%     
==========================================
  Files         178      178              
  Lines       13836    13835       -1     
==========================================
- Hits         9097     9096       -1     
  Misses       4124     4124              
  Partials      615      615              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zakisk]

@chmouel when I was running it manually it was working as expected but in E2E test I am getting below warning and PipelineRun wasn't being triggered.

{"level":"info","ts":"2024-12-28T07:43:27.302Z","logger":"pipelinesascode","caller":"events/emit.go:48","msg":"User jerel-app[bot] is not allowed to trigger CI by gitops comment on this repo.","commit":"e7b0f7f","provider":"github","event-id":"69aae510-c4ef-11ef-9d95-c02b0678b4a6","event-sha":"e1f82c340fb1f36dc68fb0522212ba09c427eb31","event-type":"no-ops-comment","namespace":"pac-e2e-push-6xk8l"}

[zakisk]

while I am seeing that in E2E tests of this PR pipelines-as-code-ci GH App is triggering PR and my GH App has all permissions specified in docs.

[zakisk]

apart from this issue, rest is /LGTM