fixing encoding issue with useragent string processing in da tornado

- tornado get_argument has a bad time with non-utf encodings. and
apparently userAgent strings are supposed to be latin1 and we had some
with extended ascii (accent) characters that were causing issues. now
fixed.
- experimented with not requiring a corresponding win notice with
click/conversion aggregation (lost some win notices due to excessive
packet loss for a time) but other problems arose. it could still be done
but not worth getting into other required other changes at this time.
(sql that does the aggregation itself wants to find win notice as well i
believe, which is used in other parts of the code)
- made rabbit monitor allow up to 10 messages in queue before reporting
that is is falling behind (was hitting the old 5 messages limit from
time to time due to increased traffic)