Do not always filter Serial Port profiles out anymore on Android

1.) If we find a custom and SPP uuid we create only on service
using custom uuid as service uuid and SPP as service class uuid.
THis is the recommended way. Any remote service should really
advertise a custom uuid. Unfortunately this is not always the
case on some embedded devices. Hence we need to cover the cases
below.

2.) If we find a custom uuid only we create a service which uses
the custom uuid as service uuid but we do not set a service class.

3.) If we find a SPP uuid only, we create a service which uses SPP
as service uuid and as service class uuid. This is no problem as
Android's connectToRfcommService() call explicitly permits an SPP
uuid as connection parameter.

4.) We find none of the above the problem doesn't exist in the
first place and no service was found.

Task-number: QTBUG-38140
Change-Id: I2e9080f65b98db23782264ef9e62a410ab9f91f1
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Add Qt 5.3.0 change log for QtNfc and QtBluetooth

Change-Id: Id489adfe1cfb4c652907e67950b8a12bf1c18c8c
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>