Latitude longitude filter

Latitude/Longitude filter:

This filter let you define points and a radius in order to define areas. Then, the filter could discard bid requests not belonging to those areas.

Agent config example to use the filter:

{
...
"latLongDevFilter": [{"lat": 37.123, "radius": 15.5, "long": -92.456}]
...
} 

I meant calculating the MBR of all the combined points such that the filter can start by doing this one quick test to determine if it has anything to do at all. The usefulness of this will depend on how spread out the bid request traffic your seeing. For example, if you're receiving bid request traffic for the entire US but you're only looking for BR that are within a small radius of 100 point or so in New York then having the MBR of these 100 points could allow you to quickly rule out 90%+ of the traffic without having scan the 100 points. 

Unfortunately, updating the MBR as configs are being removed pretty much means that you have to recalculate it from scratch if the point is defining one of the sides of the MBR.

In any case, don't worry too much about fancy data-structures for now, I was just thinking of possible improvements to avoid linear complexity wherever possible. We can improve it later if we find the need for it.