Add AsyncStringFeatureParser and use plain
XMLHttpRequest in the KML example

Since the content-type on github.io is application/octet-stream we need
to implement an Async string based parser interface in the KML parser.
Also use plain XmlHttpRequest in the example instead of jQuery Ajax since
the vector-features example also uses that.
Fix ol.Geolocation and ol.GeolocationOptions export
Fix use of dispose in ol.parser.KML
Fix use of dispose in ol.control tests
Fix use of dispose in ol.control.ZoomSlider tests
Fix use of dispose in ol.layer.Layer tests
Fix use of dispose in ol.layer.Vector tests
Fix use of dispose in ol.Map tests
Fix use of dispose in ol.renderer.webgl.ImageLayer tests
Merge pull request #642 from fredj/geolocation-export

Fix ol.Geolocation and ol.GeolocationOptions export
Exporting KML parser options

This is necessary because application developers need to be able
to configure the KML parser.
Making the linter happy

... although jsdoc files are none of the linter's business.
Merge pull request #641 from bartvde/kmlexample

Add AsyncStringFeatureParser and use plain (r=@ahocevar)
Merge pull request #638 from ahocevar/kml-options

KML rendering in advanced compilation mode. r=@bartvde
Add map property "target"
Map target may be undefined
Add a teleport map example
Remove unused ol.Object.prototype.changed
Change ol.source.WMTSOptions.projection type to ol.ProjectionLike

Same type as base class.
Merge pull request #645 from fredj/ol.object.changed

Remove unused ol.Object.prototype.changed