Improve query*Features documentation

[jfirebaugh]

The following caveats for feature querying were included in the documentation for the featuresCallback for featuresAt / featuresIn:

 * Note: because features come from vector tiles or GeoJSON data that is converted to vector tiles internally, the returned features will be:
 *
 * 1. Truncated at tile boundaries.
 * 2. Duplicated across tile boundaries.
 *
 * For example, suppose there is a highway running through your rectangle in a `featuresIn` query. `featuresIn` will only give you the parts of the highway feature that lie within the map tiles covering your rectangle, even if the road actually extends into other tiles. Also, the portion of the highway within each map tile will come back as a separate feature.

We should restore and adapt this text for the documentation for queryRenderedFeatures and querySourceFeatures.

EDIT: The scope of this ticket has expanded. Please see #2429 (comment)

[jfirebaugh]

Another thing to document is the decision in #2321 about the behavior for wrapped features.

[ansis]

Another thing to document is that the order of the features is top-down based on the style.

[lucaswoj]

Todo

• restore query method caveats Improve query*Features documentation #2429 (comment)
• document is that the order of the features is top-down based on the style. Improve query*Features documentation #2429 (comment)
• document is the decision in fix queryRenderedFeatures box across dateline #2321 about the behavior for wrapped features
• document that these methods only operate on visible features
• explain the difference between querySourceFeatures and queryRenderedFeatures
• remove the assertion that querySourceFeatures includes a layer property on features
• clarify that query*Features returns an array of features rather than a GeoJSON feature collection
• state that querySourceFeatures requires params.sourceLayer for vector sources