abstract `rest_api` module into a seperate library

[2bndy5]

I've been pondering ways to reuse the rest_api module in other projects that want to post feedback in a CI workflow.

Abstracting the module into a standalone library would require callback function pointers (and/or possibly trait implementations) to keep cpp-linter algorithms separate from REST API usage. This mainly includes

• creating comments' content
• the comment marker prefixed to each comment (<!-- cpp linter action -->)
• CLI options specific to posting feedback
• ??? still investigating

Additional ideas

Create bindings for the abstracted library for use in python and/or node.js. Using rust async runtimes (like tokio) in python is not yet officially supported in pyo3 project (see pyo3 docs).

This abstracted library wouldn't be specific to cpp-linter, so I should migrate the library to my own github account.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[2bndy5]

I started a project 2bndy5/git-bot-feedback which aims to resolve this. It doesn't have PR review support (yet). I might also create bindings to python and node.js in the future. For now, I'm just focused on abstracting the useful REST API implementations from here in a way that is agnostic of cpp-linter.