Make it obvious what platforms are supported by QtSensors.

Also, this brings the front page layout somewhat further
in line with qtlocation & qtconnectivity API docs.

Change-Id: I5e54ae388892dcb2a806c4775828abcdc81eb79d
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Create a new sensor type for distance.

Create a new sensor type for distance. This sensor type supports new hardware sensors
that can measure physical distance from the device, in centimeters. The API is designed
to mimic the Android API for proximity (TYPE_PROXIMITY), so that if a given proximity
sensor only supports a binary measurement (near vs far), then instead of reporting distance
in cm, the QDistanceSensor will return the max range value to represent far, and a lesser
value to represent close. Using this definition should simplify implementation.

The main reason for not implementing this as a new property of QProximitySensor is that
clients of QProximitySensor have made the assumption that they will receive the readingReady
signal if and only if the reading has changed from near to far or vice versa. Adding a
distance property will break that assumption, as distance has a higher degree of precision.

Change-Id: Ia804948c78ff7391fc8b78df975cddcf861326dc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Merge remote-tracking branch 'origin/stable' into dev

Change-Id: I6b203a32b2f52255ae4e63cfb279e762458c0128