WIP: Forgejo / Gitea support

[lumarel]

As already mentioned in the issue currenlty looking into making megalinter work for Forgejo / Gitea.
Mostly it seems like it will just work, there are only a few details that make it break.

This is mostly a PoC for now, still have to test if the changes of the reporter actually work,
though if you want you can already give feedback, might just not be finished yet.

Fixes #7779

Proposed Changes

Currently the plan is to:

1. Add documentation how to setup the workflow
2. Adapt GithubCommentReporter to work with the Quirks of the different platform

Readiness Checklist

Author/Contributor

• Add entry to the CHANGELOG listing the change and linking to the corresponding issue (if appropriate)
• If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, enhancement, infrastructure, or performance

[nvuillam]

azure-pipelines ? ^^

[lumarel]

Oops, I took this one as the template and must have overlooked that 🙂

[lumarel]

Just a short headsup, it seems like I have to replace nearly all pygithub commands with requests calls, first full draft might still be lots of conditions in the GithubCommentReporter, but in the end it might be better to split it out into it's own reporter.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this pull request should stay open, please remove the O: stale 🤖 label or comment on the pull request.

[nvuillam]

@lumarel i agree, if the github libraries are not matching forgejo / gitea apis, let's create new reporters :)