Fix QGeoRouteReplyOsm::networkReplyFinished

It can happen that the osm router does not find a route between the
specified points. In this case it returns a json object with a status
code other than 0 and an error message.
This commit notifies the app developer that an error occurred and
that no valid route is available.
Prior this it was not possible to catch the error message.

Change-Id: I172ae3cf9dfcd80e5a162110178203084071c9b0
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Avoid potential double deletion when handling OSM route replies

Change-Id: I15ab944e7b9e7cecc8ff9122183c438fd006e65b
Reviewed-by: Robin Burchell <robin+qt@viroteck.net>
Fix fitViewportToMapItemsRefine

The item counter was broken. Therefore the bounding box calculation
only worked under certain circumstances.
This commit removes the circle special case calculation, which is
superfluous, and treats all map items the same way.

Change-Id: Ida0a6cf695fb151132bc867eb30ecb834a5bf6c5
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Merge remote-tracking branch 'origin/5.3' into 5.4

Change-Id: I48f866a8fbb8af18dee640eada24556d097059b0
Merge "Merge remote-tracking branch 'origin/5.3' into 5.4" into refs/staging/5.4