Scale increment and decimal fields according to cooked unit, so that the decimal and increments provided by meta data still work in the cooked display

All qsTr calls done
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

All facts are numeric, atm. this means that the input should only
accept numbers. it already had the     inputMethodHints:   Qt.ImhFormattedNumbersOnly
option, but for some reason it still accepted letters and symbols.
by adding a     validator: DoubleValidator {} we limit the characters
to numbers only - and if the value is a integer, it will still work.

Tested by adding waypoints on the map & messing with the GPS coordinates.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

Map control use different border color based on map type

Also can handle additional components coming through after default
component is complete

I removed some needed headers from a top level file which then causes a
ripple effect downstream

Conflicts:
	src/FactSystem/ParameterLoader.cc

 - Request list of all parameters, expecting device to lead each component with _HASH_CHECK cache value
 - Test for hash collision, if so our cache is valid and respond with _HASH_CHECK to stop listing
 - Else: let listing continue as normal to get updated param values
 - Store each cache by systemID + componentID

For #2586

Plumb through initial object mode on Vehicle