chore: Migrate CI to forgejo

The development scripts and related Kubernetes resources were updated to
reflect the change from Gitea to Forgejo. This involved renaming files,
updating variable names, and modifying configuration to use Forgejo's
specific paths and image. The core functionality of setting up a Git
provider for testing purposes remains the same.

Add some comment on policy.go so the e2e can trigger and test this
change.

Jira: https://issues.redhat.com/browse/SRVKP-9991
AI-assisted-by: Google Gemini
Signed-off-by: Chmouel Boudjnah <[email protected]>

Author: chmouel

hack/dev/kind/gitea/README.md hack/dev/kind/forgejo/README.mdhack/dev/kind/gitea/README.md renamed to hack/dev/kind/forgejo/README.md

@@ -1,18 +1,18 @@
-# Gitea in a Pod for PAC
+# Forgejo in a Pod for PAC
 
-This will :
+This will:
 
-- spin a gitea deployment into a namespace
-- create a ingress to a URL
+- spin a Forgejo deployment into a namespace
+- create an ingress to a URL
 - create a repository
 - create a user/password
 - create a token for user/password
-- create a empty repository
+- create an empty repository
 - create a hook to go to a hook.pipelinesascode.com URL
 - create a deployment with gosmee to forward smee URL to the pipelines as code controller
-- create a rpo crd to bind to it.
+- create a repo crd to bind to it
 - create a secret for the Git provider with the token generated previously
 
-You can easily configure the script using environment variable see the top of the files for the list.
+You can easily configure the script using environment variables, see the top of the files for the list.
 
-designed to run on kind.
+Designed to run on kind.