Improve documentation for ol.Feature

This adds a bit more substance to the `ol.Feature` documentation.
> It is possible to store more than one geometry on a feature

what's the use case(s) for this? It's always easier to explain things with examples. This departs from the concept of features in formats like GeoJSON or KML