[GithubSize] Support file paths via query parameter

[Kryptonzy]

Summary

Add a query-parameter form of the GitHub file-size badge so filenames that look like badge output formats can be requested without ambiguity:

/github/size/badges/shields.json?path=package.json

The existing path-based form remains supported for backward compatibility.

Fixes #10548.

Root cause and approach

In /github/size/badges/shields/package.json, Shields interprets the final .json as the requested badge format. The service consequently receives package as the file path and asks GitHub for the wrong file.

The service route now permits the path segment to be omitted and accepts path in its validated query schema. handle() prefers the existing route path when present, otherwise uses the query path, and returns a clear path is required error if neither is supplied. A second OpenAPI route documents the query form. This adds an unambiguous entry point without breaking existing badge URLs.

Verification

• npm run test:services -- --only=GithubSize --fgrep='filename matching a badge format' — 1 passing.
• npm run test:services -- --only=GithubSize --fgrep='File size without a path' — 1 passing.
• The success regression mocks GitHub's contents API, asserts the request reaches /contents/package.json, and verifies a 1 KiB badge.
• npx --no-install eslint services/github/github-size.service.js services/github/github-size.tester.js — passed.
• npx --no-install prettier --check services/github/github-size.service.js services/github/github-size.tester.js — passed.
• npm run defs — passed.

Scope

Only GithubSize routing/query validation, its OpenAPI definition, and two focused service tests change. Existing route-path and branch behavior are retained.

AI assistance

OpenAI Codex (GPT-5) was used to inspect the route/format interaction, implement the minimal backward-compatible change, and run/review the tests and final diff. The repository does not prohibit AI-assisted contributions; this usage is disclosed explicitly.

[github-actions]

	Messages
📖	✨ Thanks for your contribution to Shields, @Kryptonzy!

Generated by 🚫 dangerJS against 03765a2

[PyvesB]

Thanks for the contribution @Kryptonzy ! Perhaps we could stop explicitly supporting the old route, and add a redirector to the new one with the query path parameter, for backwards compatibility. @DCjanus what do you think?