caronc/apprise-api v1.3.0 on GitHub

Overview

This is a signifigant release that refactors almost the entire website giving it a much more polished/improved look.

Improved instructional text and layout in the configuration template.
Minor template clean-up and formatting alignment for the help content.
Updated the configuration list view to support API based calls so it can return JSON when requested,
instead of always rendering the template.
- This enables programmatic consumption of configuration IDs/keys.
The API version is now exposed in headers in addition to the Apprise library
version, reducing confusion about the relationship between the two packages.
/cfg/<key> now accepts POST in addition to the previous retrieval approach acting exactly how /get/<key> POST works. /get/ would return the users configuration when it was posted to. It makes sense to use /cfg/<key> as well for users who copy/paste URL's from their Apprise API instance directly (from the browser URL). Basically /cfg/<key> is now an alias of /get/<key>
- /get/<key> remains supported for backwards compatibility. No plans on removing this either.
Expanded swagger.yaml substantially to better document the service.
- Added a dedicated docker-compose.swagger.yml to launch Swagger UI pointing
  at the repository swagger.yaml without altering Apprise-API runtime.
```
docker compose -f docker-compose.swagger.yml up -d
# Browse:
#   http://localhost:8001
```
improvements to README.md
heath checks are now live when viewing the website
heavy changes to workflow:
- development environment is now just tox -e runserver
- improvements to linting and formatting

Bump actions/checkout from 5 to 6 in the actions group by @dependabot[bot] in #281

Full Changelog: v1.2.6...v.1.3.0