#### 📖 Summary
<!-- Provide a summary of your changes. Describe the why and not how. -->
#### 📑 Test Plan
> 💡 Select your test plan for the code changes.
- [x] CI pipeline tests
- [ ] Custom test
- [ ] No test plan
##### Details / Justification
<!-- Add your test details or justification for missing tests here. -->
#### 📚 Additional Notes
<!-- A place for additional detail notes. -->
Reviewed-on: #6
#### 📖 Summary
<!-- Provide a summary of your changes. Describe the why and not how. -->
#### 📑 Test Plan
> 💡 Select your test plan for the code changes.
- [x] CI pipeline tests
- [ ] Custom test
- [ ] No test plan
##### Details / Justification
<!-- Add your test details or justification for missing tests here. -->
#### 📚 Additional Notes
<!-- A place for additional detail notes. -->
Reviewed-on: #1
If a repo has been tagged with gitea-pages-allowall we don't need an
extra gitea-pages branch with a toml configuration.
This makes it easier for repos that can just expose every branch
If we have a domain configured eg giteapages.io then besides the normal
user.giteapages.io and org.giteapages.io we also support
repo.user.giteapages.io / repo.org.giteapages.io
branch.repo.user.giteapages.io / branch.repo.org.giteapages.io
If we don't find a repo, we search for the gitea-pages repo if this
exists, has the gitea-pages topic tag and has a gitea-pages branch we
will use this to do a file lookup.
We don't need a gitea-pages.toml config file for this repo.
