fix(repos): escape the path in create_or_update_file

[jayhemnani9910]

Summary

create_or_update_file sent the file path into the request URL unescaped, so a path with # or ? was cut there and the content was written to a different file. The path is now escaped segment by segment before the write.

Why

Fixes #3427

go-github's CreateFile puts path into the URL as is, while GetContents (used for the existence, SHA and symlink checks) escapes it. So docs/C#/intro.md was checked as the right file but written as docs/C.

What changed

• CreateOrUpdateFile passes escapeGitTreeish(path) to CreateFile.
• New test Test_CreateOrUpdateFile_EscapesPath: writes docs/C#/intro?.md and checks the PUT goes to .../contents/docs/C%23/intro%3F.md. Without the change the PUT goes to .../contents/docs/C.

MCP impact

• No tool or API changes
• Tool schema or behavior changed
  Paths with #, ? or % are written to the file that was asked for. No schema change.
• New tool added

Prompts tested (tool changes only)

• Not run against the live API (it would need a write to a real repository); covered by the mock test above.

Security / limits

• No security or limits impact
• Auth / permissions considered
• Data exposure, filtering, or token/size limits considered

Tool renaming

• I am renaming tools as part of this PR (e.g. a part of a consolidation effort)
  • I have added the new tool aliases in deprecated_tool_aliases.go
• I am not renaming tools as part of this PR

Lint & tests

• Linted locally (golangci-lint v2.14.0, the version ./script/lint pins: 0 issues)
• Tested locally with go test ./...

Docs

• Not needed
• Updated (README / docs / examples)

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.