[fix] m_remoteSensorManager can be nullptr

But it seems it does not solve incorrect initialization in the case
manager interface is nullptr: init() for different sensors does not
check initDone

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
split initSensor() to template function and function

most of initSensor() does not depend on template param, so it is
better to split it -> less code should be generated

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
[sensorfw] do not use sensor manager if it is invalid

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
correct class members initialization order

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
assert sensor interface is not null

From what I saw according to logic it should not happen so using
Q_ASSERT for better maintainability

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
check local interface pointer in SensorfwTapSensor::start()

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
[manager] tracing plugin loading

Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
Merge pull request #5 from deztructor/fix-remote-sensor-man-null-access

Fixing remote sensor mananger null pointer access