Turning @tschaub's FeatureAgent into an event extension.

See http://trac.osgeo.org/openlayers/browser/sandbox/tschaub/select/lib/OpenLayers/FeatureAgent.js. Tests are still missing, but this already works on mobile devices and with Canvas layers. Another possible task would be to make the SelectFeature control use this instead of the Feature handler - then we could get rid of the RootContainer layer for multiple layer selection.
Move some touch logic to the `handler` base class.
Avoid breaking the "OpenLayers.String.format" execution when searching for an attribute in an undefined object.
don't try to update the matrix in setMap since it's too early and done later in moveTo
Move detection of map procjection to merge function, check for successful response and fix tests.
Fix copyright date
Restore arguments parameter to make function future-proof
Restore layer alias variable
Restore layer alias variable
Remove unnecessary success check
Adjust language code from 'pt-br' to 'pt-BR'

Portuguese Brazilian translations were not loaded due to this.
Avoid touching the geolocation object until needed

IE9 leaks when `navigator.geolocation` is accessed (see #461).  The goal of this change is to avoid that leak in builds that include the Geolocate control but do not use it.
Using the correct parent node

When we have a Google base layer, the parent node of the base layer's div
will be a different one.
Merge pull request #903 from ahocevar/903

Google Maps and WMS layer Backbuffer error. r=@mosesonline
Simplifying and unhacking the ModifyFeature control

With two nested controls (DragFeature, SelectFeature), which - among
others - activated two OpenLayers.Handler.Feature instances, the
ModifyFeature control was fragile and hard to debug.

The issue that @iwillig, @bartvde and myself tried to track down was
that the two Feature handlers interfered with each other, making it hard
to select features on mobile devices, and causing points to jump during
dragging because of not updated last pixel positions.

With this refactoring, there are no more nested controls. All that's left
is a Drag handler. All tests pass. I had to remove one test that checked
for dragging of an unselected point while another was selected, because
now (and partially even before this change, thanks to the ugly drag
handler hack that is now removed) dragging a point will also select it,
saving the user an extra click.
Increasing point radius for easier touch selection
Merge pull request #730 from pgiraud/wmts

don't try to update the matrix in setMap since it's too early and done l...
Addressing @bartvde's review comments
Merge pull request #913 from ahocevar/modify-feature

Simplifying and unhacking the ModifyFeature control. r=@bartvde
Thicker strokes make it easier to select line segments