hyperswitch

239cb2d1 - feat(analytics): add payment method audit table for API events and tag internal service traffic

feat(analytics): add payment method audit table for API events and tag internal service traffic The modular payment methods service publishes its API events to a separate Kafka topic today. Once it publishes to the shared `api_logs_topic`, its events land in `api_events` alongside router traffic, which needs two things to be usable: - A payment method scoped audit table, in the same shape as the existing payment (`api_events_audit`) and payout (`api_events_payout_audit`) audit tables: `api_events_payment_method_audit` keyed on a mandatory `payment_method_id`, plus the materialized view that populates it - A way to tell service-to-service calls apart from direct merchant traffic on the same routes: `api_flow` is now suffixed with `_microservice` when the request authenticated with the internal API key Also implements `ApiEventMetric` for the v2 token data, network token status check and tokenization request/response types, which previously emitted untyped `Miscellaneous` events and so carried no payment method identifier for the audit table to key on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>