[GithubLastCommit] [GitlabLastCommit] [GiteaLastCommit] Support file path for last commit

[ReubenFrankel]

Closes #7351

Adds support to resolve last commit for a given file path, for GitHub, GitLab and Gitea services.

[github-actions]

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

Generated by 🚫 dangerJS against 4d9a24c

[github-actions]

🚀 Updated review app: https://pr-10041-badges-shields.fly.dev

[chris48s]

Thanks. This looks good, but I think we could do with improving the error handling/messages slightly.

On the GitLab and GitHub APIs, if we specify a path that doesn't exist, we get back an empty array. This means the response fails schema validation.
Tbh, I suspect this probably also happens for a repo with zero commits, but this is not something that has come up before.
It would be nice to throw a more informative error in this cases. My suggestion would be we remove the .min(1) requirement from the schema and then after we fetch we throw a NotFound('no commits found') if there are zero items in the array (to cover both situations).

With the Gitea API, if the path doesn't exist, we get a 404 back and throw the error "user or repo not found". I think for this case, we can just amend the error message to "user, repo or path not found"

We should also have test cases for the errors.

[chris48s]

Just looking over your other similar PR for bitbucket, you've already adopted the same pattern I described for the error handling there 👍

[ReubenFrankel]

@chris48s I've made the suggested changes - tests are passing locally so not sure why they are failing in CI (can't see from the log).

[github-actions]

🚀 Updated review app: https://pr-10041-badges-shields.fly.dev

[chris48s]

Thanks. This looks good.

Looks like the test failures were just a transient failure with some requests timing out.