feat(repos): add repository configuration edit (rename / archive / deploy keys / autolinks)

[nemolize]

Surfaced by the coverage-table audit in #189: the Repository configuration edit row is ❌ — an entire feature area with no coverage.

gh CLI counterpart

• gh repo edit — rename, description, homepage, visibility, features (issues / wiki / projects), merge options
• gh repo archive / gh repo unarchive
• gh repo rename <new-name>
• gh repo sync — sync a fork with upstream
• gh repo deploy-key add / list / delete
• gh repo autolink create / list / view / delete

Notes

• Rename / archive / delete-key are all destructive; align care level with the existing delete_repository handling.
• Official github/github-mcp-server also lacks these (only CreateRepository / ForkRepository / star/unstar in pkg/github/repositories.go).
• Splitting into a metadata-edit phase (rename / archive / edit) and a keys/autolinks phase makes review manageable.

Related

• README table gap surfaced in docs(readme): surface untracked gh CLI coverage gaps in comparison table #189
• Existing repo admin (create / fork / delete): feat: add Repo admin tools (create / fork / delete repository) #107