feat: Add row_changes_cap_per_file parameter to datasets comparer

[jcpitre]

Adds an optional row_changes_cap_per_file parameter to the gtfs_datasets_comparer HTTP function, controlling the maximum number of row-level change entries included per file in the generated changelog. Defaults to 10000 to prevent excessively large outputs on big feeds. Set to 0 to omit row-level detail entirely, or null for no cap.

Invalid (non-integer) values are rejected early with a clear error message rather than bubbling up as a generic exception.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
• Add or update any needed documentation to the repo
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues
• Include screenshot(s) showing how this pull request works and fixes the issue(s)

[davidgamez]

LGTM