Exacheck

Fixes:

- Reap zombie processes and respawn on failure (fixes [8](https://github.com/exacheck/exacheck/issues/8))

Misc:

- Update Sentry and dnspython releases

Changes:

- Add support for Python 3.10 and Python 3.12
- ExaBGP will be built from source if using Python 3.12 (using the 4.2 branch)
- Dockerfile changes to add support for Python 3.12:
- Install ExaCheck from git rather than PyPi to allow easier version customisation
- Make sure wheel/setuptools/pip is up to date

Misc:

- Update Semgrep and pydantic releases
- Remove requirement on types-requests; this is not needed for production usage
- Re-format pyproject.toml - use groups for development/typing/formatting/testing

Fixes:

- `http` check method fails to parse the URL correctly for IPv6 hosts; IPv6 address must be enclosed with `[]`

Fixes:

- Log file `count` option was not being used at all; log files would rotate but never be cleaned up
- If a `host` value was provided for the `http` check method the value was being ignored; the host was overwritten from the hostname in URL

Fixes:

- Correct the logging event types for announce/withdraw of routes for log filtering to work correctly
- Fix metric attribute naming error

Changes:

- Log exceptions when sending routes to ExaBGP
- Update syslog format string
- Include hostname when logging to remote servers
- Include timestamp when logging to remote servers or when structured logging is used

Features:

- Add the following options for Sentry; values are set to the Sentry defaults:
- `attach_stacktrace`
- `include_local_variables`
- `debug`
- Move Sentry profile sample rate out of experimental configuration

Fixes:

- Formatting fixup in `__version__.py`
- Ensure STDOUT is flushed on route announce/withdraw
- Define `app_url` for Apprise
- Change line breaks for Apprise notification as they are broken in Slack
- Debug or trace level logging must be enabled to log the Python filename/line number/function name in file/syslog

Changes:

- ExaCheck internal configuration (eg. for the `live_reload` feature) has been migrated out of the base `Settings` class. Instead, ExaCheck configuration now resides in its own `settings.ExaCheck` class.