[iioadaptor] Allow overriding iioDevices' scaling factor. Fixes MER#2053

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

Rename sensorfw-qt subpackage docs to doc and make packaging information
more consistent with other packages.
Signed-off-by: Tomi Leppänen <tomi.leppanen@jolla.com>

Allow disabling / enabling sensors plugins via config entries like:

  [available]
  proximitysensor=True
  magnetometersensor=False
  lidsensor=Feature_CoverSensor
  orientationsensor=Feature_GyroSensor|Feature_AccelerationSensor

Where:
- "True" means that loading of the sensor plugin is made available
  via D-Bus interface and can be loaded.
- "False" means the plugin will not be loaded and sensor is not
  made available via D-Bus
- "Feature_*" means that sensor availability is checked from hw
  settings. If sensorfwd is compiled without ssu-sysinfo support
  these will be treated similarly to "True".
- "" (or plugin that does not have config entry) is taken as "True",
  but a warning is logged in case of sensor plugins.

If a plugin that is enabled in configuration fails to load, it is
marked as not available until sensorfwd restart.

Add new D-Bus method calls:
- availablePlugins() lists all available plugins
- availableSensorPlugins() lists available sensor plugins (which,
  when loaded, make new sensor objects and interfaces available)
- pluginAvailable(name) can be used to check whether a named plugin
  is installed and available

Package default sensor availability configuration file that disables
all sensors except those that can be evaluated based on the hw
settings configuration.

Add example of device specific configuration file - these should be
installed from hw adaptation packages and can override the defaults.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Android services/actions launched by droid-hal-init, queued oneshot
scripts and sensorfwd are executing in parallel during bootup. During
especially the 1st boot the scheduling of tasks can lead to sensorfwd
getting hold of nonfunctional sensor hal.

Delaying sensorfwd startup until oneshot scripts have been executed
makes it less likely for the problem to surface.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Just because I forgot to add mer-bug reference.

[patch] Take patches from LuneOS. Fixes MER#1879

Using systemd specific startup notification is preferable over cusrom
daemon forks.

Add support for systemd-notify and use it instead of forking.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Since sensorfwd is using Type=forking, specifying a BusName leads to
systemd complaining: "sensorfwd.service: Service has a D-Bus service
name specified, but is not of type dbus. Ignoring."

Remove BusName specification from the sensorfwd.service file.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Also the commits were lacking a bug ref, so adding one here.

[hybris-adaptors] add powerstate_path as parameter to start and stop the sensor. Fixes MER#1753

Only Qt5 is supported.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

The "jobs" macro is non-standard and won't use multiple cores when
building under mb2.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

The config files should be installed per device