fix(#907): remove get_files() workarounds for fixed pyforgejo spec

[fullsend-ai-coder]

Summary

• Remove the runtime warning from ForgejoProject.get_files() that was added as a workaround for the incorrect Forgejo OpenAPI spec (which caused pyforgejo validation failures)
• Unskip test_get_files integration test, now that pyforgejo >= 2.0.1 handles the API response correctly
• Update recorded test data URL to match current pyforgejo URL generation (root contents endpoint no longer includes a trailing slash)

Testing

• All 102 Forgejo integration tests pass (previously test_get_files was skipped)
• ruff linter passes on changed files

---

Closes #907

Post-script verification

• Branch is not main/master (agent/907-remove-get-files-workarounds)
• Secret scan passed (gitleaks — 8a9787200dc24411e2e0294178c6def0cbb3bbef..HEAD)
• PR body secret scan passed (gitleaks — no-git)
• Pre-commit hooks passed (authoritative run on runner)
• Tests ran inside sandbox

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 5:02 PM UTC · Completed 5:11 PM UTC
Commit: 002b17b · View workflow run →

[fullsend-ai-review]

Review

Findings

Medium

• [api-contract] pyproject.toml:47 — The PR removes the runtime warning and unskips the test based on the fix being in pyforgejo 2.0.1, but pyproject.toml still allows pyforgejo>=2.0.0 which contains the broken spec. A user installing ogr fresh could resolve pyforgejo==2.0.0 and hit the original validation failure in get_files() — now without the warning that previously explained the issue.
  Remediation: Bump the minimum version pin from pyforgejo>=2.0.0 to pyforgejo>=2.0.1 in pyproject.toml.

---

Labels: PR modifies Forgejo service integration code and fixes a bug tracked in issue #907

[centosinfra-prod-github-app]

Build failed.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/79b30ef8797347c495cddf4850eac1f0

❌ pre-commit FAILURE in 3m 29s
❌ ogr-tests-pip-deps FAILURE in 11m 32s