Harden HoneySAP core lifecycle, event delivery, and Docker-first deployment

[martingalloar]

• Harden configuration loading and startup:
  • redact sensitive configuration values in logs;
  • use restricted YAML loading;
  • validate listener topology before launch;
  • apply gevent monkey-patching at process startup.
• Improve event, session, and feed reliability:
  • preserve binary evidence unambiguously in serialized events;
  • add schema version, event ID, sequence, UTC timestamp, and campaign correlation;
  • bound event/session/campaign retention and expose queue metrics;
  • isolate feed delivery so one failing or slow feed does not block others.
• Improve routed and forwarded traffic handling:
  • retain exact SAPRouter → Forwarder lineage through parent_session;
  • add bounded concurrent relays shared by direct and virtual Forwarder paths;
  • track active forwarding sockets for orderly shutdown;
  • document how to interpret session, campaign, and parent_session.
• Refresh deployment and documentation:
  • remove Vagrant/Ansible deployment paths in favor of Docker;
  • align Docker Compose, Dockerfile, internal profile, and Message Server HTTP-to-ICM redirects;
  • replace the static architecture asset with a generated diagram;
  • add concise architecture, service-selection, event interpretation, and installation guidance.