Forgejo's commits endpoint filters on `sha`, not `branch`. Sending
`?branch=<name>` was silently ignored and the API returned the default
branch's commits for every ref, so branch resolution appeared to work
while always yielding the same list.
Rename the parameter to `ref` (a branch, tag, or sha) and send it as
`sha`, documenting that the slot name is Forgejo's choice while the value
is a caller-supplied git ref.
The flat commits payload is GitHub-shaped (`sha`, `commit.message`,
`html_url`, `created`) while the nested branch commit uses `id`,
`message`, `url`, and `timestamp`. Give each Commit field an
AliasChoices/AliasPath covering both shapes so one model serves the
/branches and /commits endpoints, then map commits through it instead of
returning raw dicts under a `list[Commit]` annotation.
Also annotate get_branches' limit/page to match get_commits.