Extracting and abstracting to enable use with Vela

[colindean]

My org uses Vela CI for CI/CD pipelines. I'd love to be able to use this tool with Vela, but it seems pretty tightly coupled to GitHub Actions at the moment because spots like

diff-poetry-lock/diff_poetry_lock/run_poetry.py

Line 115 in ee9be76

api = GithubApi(settings)

I don't know what my bandwidth will be to undertake this myself, but minimally, having a code path that would enable comparing two poetry.lock files without using the GitHub API would accomplish the task enough for me to wire it up as a pattern for Vela and then advance to building a Vela plugin around it.

What do you think?

[colindean]

Reading more, I think we might be able to use a lot of the plugin as-is, but need to be able to send in some different envvars and set the GitHub host, e.g.

diff-poetry-lock/diff_poetry_lock/github.py

Line 34 in ee9be76

f"https://api.github.com/repos/{self.s.repository}/issues/{self.s.pr_num()}/comments",

and

diff-poetry-lock/diff_poetry_lock/github.py

Line 43 in ee9be76

f"https://api.github.com/repos/{self.s.repository}/issues/comments/{comment_id}",

and such would need to use an overrideable GitHub API hostname.