production trust and operations diagnostics

[vishalanandl177]

Summary

• Add a production diagnostics engine for DRF-API-Logger configuration, database readiness, queue health, payload limits, masking, and profiling risk checks.
• Expose manage.py drf_api_logger_doctor with text/JSON output and configurable failure threshold for operations and CI usage.
• Document the production doctor workflow in README, operations docs, and developer testing guidance.

Validation

• python -m django test tests.test_diagnostics tests.test_management_commands tests.test_docs_content --settings=tests.test_settings --verbosity=1 - 44 tests passed.
• Full package suite was run before push: python -m django test tests --settings=tests.test_settings --verbosity=1 - 243 tests passed.
• Smoke runner was run before push: python test_runner_simple.py - 27 tests passed.
• Coverage was checked for the new diagnostics surface: drf_api_logger/diagnostics.py and drf_api_logger/management/commands/drf_api_logger_doctor.py both reported 100% in the targeted coverage report.
• Demo E2E against J:\projects\drf-demo on http://127.0.0.1:8000 verified doctor output, warning failure threshold, HTTP log persistence, 500 logging, and password masking.

Notes

The demo app intentionally reports one warning (DRF603) because profiling sample rate is configured at 1.0; default --fail-level error passes with zero errors, while --fail-level warning exits nonzero as designed.