Improve logging around geo restrictions, routing decisions

[elsloo]

Improve logging such that we can clearly identify when an IP is rejected due to geo restrictions, or any restriction in general. Enhance any other routing decision logging as needed, however, as with all logging changes be mindful of the amount of data logged per request, and how that amount of data changes with a rejected request vs one that's successful.

[elsloo]

If the X-MM-Client-IP client header is present, Traffic Router logs that IP in the chi field instead of the IP of the client. This makes troubleshooting and finding the source address very difficult, as the only option is to check the wire using tcpdump.

Please ensure that both IPs are logged; potentially move X-MM-Client-IP to the request header logging and only use the client IP in the chi field