Support for Gitea & ForgeJo CI

**What?**

Currently, the CI integration generated by dist only works for GitHub Actions. I would like to propose extending that support to two of the easiest-to-support, most widely used alternatives: Gitea and ForgeJo.

**How?**

This would require allowing non-GitHub repository URLs in Cargo.toml, and customizing the name of the CI directory. The limitation can be worked around manually at present, and provides an idea of the steps that would need to be taken to support the use case: my current workflow is to temporarily change the repository URL to an invented GitHub link, run `dist init`, then rename the .github directory to .gitea and change the repository URL back.

**Why?**

Although GitHub is by far the most widely used software forge, an increasing number of individuals and organizations are starting to use self-hosted solutions. Support for Gitea and ForgeJo is particularly low-hanging fruit, as they aim to be completely compatible with GitHub actions syntax.

Start by tracing the dist init workflow and how it reads the repository URL from Cargo.toml and chooses the .github directory. Compare the requested Gitea and ForgeJo workflow layout, including the manual rename to .gitea. Done means non-GitHub repository URLs generate the appropriate CI directory without manual changes.

Written by the indexing model from the issue text.