perf(common): GeolocationMiddleware runs geoip lookup on every route including health checks

[phertyameen]

Summary

app.module.ts applies geolocation enrichment globally:

consumer.apply(GeolocationMiddleware).forRoutes('*');

This means every request pays a geoip-lite lookup, including:

• /health (hit continuously by load balancers and referenced by the graceful-shutdown probe in main.ts),
• /api Swagger document routes,
• all pre-auth auth/* traffic.

Infrastructure probes get geolocation side effects for IPs that will never be users, and the lookup cost lands on the hottest paths.

Proposal

1. Exclude infrastructure paths:

   consumer.apply(GeolocationMiddleware)
     .exclude('health', 'api/(.*)')
     .forRoutes('*');

2. Audit what consumes the enriched fields downstream (the analytics module recently gained PII hashing in event metadata - confirm country/city granularity is intentional there).
3. Add unit tests mirroring the style used for CorrelationIdMiddleware, including exclusion cases.

Acceptance criteria

• Health/Swagger paths bypass geolocation enrichment.
• Business routes still receive enrichment data.
• Middleware covered by unit tests including exclusion cases.

[chiemeliesteve4-art]

Good day maintainer, i will exclude health and Swagger routes from GeolocationMiddleware to avoid unnecessary geoip lookups, verify that business routes still receive enrichment, and audit downstream use of the location fields. I will also add unit tests covering both excluded and normal routes. Thank you.