Add formatters, opt, diagnose, apprise

[nikhilvdev]

Introduce human/text/logfmt formatters and parsing utilities; preserve old formatter import path. Add Logger.opt (lazy, depth) and caller resolution, plus diagnose-mode exception locals with redaction hooks. Add AppriseAlertPlugin (optional extra), aiohttp HTTP sender, HTTPTransport hardening (max_bytes, backend selection, failure logging). Implement process-exit flush (atexit) and per-logger flush_at_exit opt-out, plus enable/disable toggles for silencing libraries. Add benchmarks and memory-budget tests, many property/unit tests, and CI changes to run benchmark job; update README, CHANGELOG and packaging metadata.

Summary

Checklist

• ruff check . passes
• mypy logquill passes (--strict on the public API)
• pytest passes, and new surface area has test coverage
• Public API additions are documented in README.md with a runnable example
• CHANGELOG.md has an entry under Unreleased
• If this touches the cross-language contract (levels, logger methods,
  record shape, transport/plugin contracts, config shape) shared with
  logquill-js, a matching tracking issue/PR is opened there

Scope

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
37485052	Triggered	Generic Password	682af03	tests/test_diagnose.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}