Do not mix common code with sensor specific

There were sensor specific functions and data interleaved with
common sensord functionality.
Add support for orientation via sensor framework

Similarly to proximity and ambient light.
Use sensorfw for detecting orientation changes

Use orientation sensor instead of listening to context kit property
change signals.

[mce] Use sensorfw for detecting orientation changes
Add datapipe for ambient light sensor data
Show current values and ranges for EV_ABS type inputs

When printing identification information about evdev device node,
current value is shown for supported ABS_XXX event types.

[evdev_trace] Show current values and ranges for EV_ABS type inputs
If possible, use evdev inputs for PS and ALS data

If ALS / PS inputs are detected during evdev probing, those
will be used instead of the data provided by the sensord.

This allows mce to apply wakelocks while processing the
sensor data, and thus avoid accidental falling back to suspend
in case there are ipc delays getting the data to mce via
sensord.

Enabling/disabling sensors still happens only via sensord.

[mce] If possible, use evdev inputs for PS and ALS data
Add macro for reading current proximity state
Fix inactivity filtering

Do all filtering before the activity state trigger is executed.
The trigger just acts on the resulting activity state.
Generate activity if proximity is uncovered during incoming call

Effectively unblanks display when proximity is not covered anymore.
Execute proximity datapipe even if there is no change
Skip tklock ipc if tklock is already set
Tone down diagnostic logging
Merge pull request #103 from spiiroin/sensorfw_evdev

Use evdev for ambient light and proximity sensor inputs