Forgejo/Codeberg backend with editorial workflow

[razzeee]

Summary

We're currently working on a website with a CMS. But we don't want to use github, so we switched to codeberg.

This is an implementation of forgejo (a gitea fork) - based on the gitea backend. Then we've amended the endpoints to be correct for forgejo and added editorial workflow handling.

Test plan

I've ran all tests locally, that work on my machine (cypress still doesn't have fedora integration)
As far as we've tested, it seems to work fine.
You can use your codeberg accounts to test here https://diday.sxda.io/admin/ but we won't merge changes :)

Checklist

Please add a x inside each checkbox:

• I have read the contribution guidelines.

A picture of a cute animal (not mandatory but encouraged)

[razzeee]

This is copied from the gittea backend and changed in name. I'm unsure how this works/it will likely need changes.

[razzeee]

You also might want to go through this commit by commit. The first one is just a copy of the gittea backend into the new folder, so changes should be obvious from the second commit.

[razzeee]

I've emptied the changelogs, as I'm unsure when they get filled

[martinjagodic]

@razzeee, thanks for the PR. If Forgejo is a fork of Gitea, could one backend support both, or did they change the API so much that it's not possible? It would be much easier to maintain one backend than 2.

[razzeee]

@razzeee, thanks for the PR. If Forgejo is a fork of Gitea, could one backend support both, or did they change the API so much that it's not possible? It would be much easier to maintain one backend than 2.

The only thing, that's on top of my head is, that the api for merging upstream is different.

I orignially started with everything in the gitea backend, but it seemed weird at the point, where the api started to be so different. And it might be hard to communicate to users (that's also a problem for codeberg) - but I guess docs might work, even if the backend name ends up weird?

Then again, I don't have access to a gitea backend, so I can't confirm, the changes work fine over there.