Update doesMapContainFeature to normalize extents

Currently we have an issue when selecting a feature on the map. If you pan the map to a new world extent, and then try to click on a feature it gets the lat/lng from the feature and although that feature is currently visible it thinks that it's not because the user is no longer in the initial (-180, 180) world extents. Then the map is jumped back to the initial extents.

doesMapContainFeature needs to be updated to normalize to it's current extents to between -180 and 180 degrees, at that point you can check if the feature is within the normalized extents and it shouldn't jump the map anymore.