Users can still enable verbosity by re-running a CI job with debugging logs enabled.

Not outputting debug logs in production will save users billable CI runtime.

try codacy coverage analysis

- Functions are properly organized in modules with appropriate names.
- REST API usage is isolated in class derived from an abstract base class that will easily allow integrating other git servers' REST API.
- clang-format output is filtered by lines (when applicable) as the XML is parsed.
- The comment is made after all clang tool output is parsed.
- All clang tool output is parsed from buffered strings (addresses #48).
- There isn't any cached files when verbosity is not set to debug mode.
- Tests can now use mocked HTTP requests (no more fear of hitting REST API rate limits).
- Updated docs to reflect the new package structure.
- CLI supports file paths/names given as positional args
- Removed dead code about previous attempt to create review comments
- Change acceptable verbosity input values to be "debug" or "10"
- Updated help strings in CLI for narrow terminals
- fix problem in "is ignored" logic
  Due to python's lazy logic evaluation, we need to check if a path is first explicitly not-ignored before checking if said source is ignored.

* hyperlink to clang-tidy diagnostic docs
* rename some TidyNotification properties
* encapsulate list of TidyNotification objects in TidyAdvice class for stronger typing

This fixes the thread-comments feature when users specify a personal access token instead of the generic `GITUHB_TOKEN`

Thankfully, we can still identify our generated comments using the action-specific HTML comment embedded in the beginning of the comment text.

Note: The HTML comment is only seen for public repositories. For private repos, the comment's body fetched by REST API is in plain text (with HTML syntax removed).

* get diff of suggestions for each files (from each clang tool)
* support PR reviews for individual tool's output
  - keep suggestions within 1 diff hunk
  - use default SHA for review commit_id
  - only create a Patch when creating a review
  - don't post reviews for PRs marked as "draft" or "closed"
* add test
* allow 2% drop (maximum) in coverage on CI checks
* get file changes for review when analyzing all files

* remove duplicated file name in tidy comment
  resolves #63
  Technically, this fixes an undesired behavior introduced in #49.
* use MD bold syntax when not using raw HTML syntax

* resolves #65

This will remove the line "No objections from ..." when it is not relevant in PR review summary comments.

Also adds a 🎉 for approved PR reviews

* change logic about traversing advice for different tools

* show cmd used to get fixes in logs

* don't add quotes around extra-arg value

* correct order of arg to post_feedback()

use kwargs to avoid mis-ordering positional args

* allow PR review summary without suggestions
  resolves #67
  This is intended to let users reduce comments posted in PR reviews.
* add test condition

The idea is to satisfy the deprecation of actions that still use node.js v16.

Actions that are bumped here use node.js v20

This is mostly taken from a comment I posted in cpp-linter/cpp-linter-action#182 with some updates.
Also reviewed other changes about the generated cli_args.rst document.

* bump codecov-action to v4

uses node.js v20 instead of deprecated node.js v16

also uses token in an env var as recommended by codecov docs

* enable dependabot

* automatically set docs' copyright and version
* doc builds use editable install of cpp-linter pkg