TR_VKEYS Left aligned #584
CFN alignments #584

costs 28B :(
Flash savings 24B

I am learning code optimisations, can someone check this comit please?
This have not to change anything, only save flash.
Version page realigned, 10B saved

\036 -Newline code for all platforms
stamp strings joined together to vers_stamp
STATS page labels joined together, 20B saved
Merge branch 'next' of https://github.com/opentx/opentx into mhotar/layout_alignments_Issue#584
newline for [All] -comment
[Taranis] Issue #554 Radio part done. We have now modes on trims.

Let's say we are configuring the Rudder Trim on phase 1:
- R:0  => Rudder trim = Rudder trim(phase 0)
- R+0  => Rudder trim = Rudder trim(phase 0) + Rudder trim(phase 1)
- R--  => Rudder trim is OFF

Still needs to be done:
- The result on screen is awful. I need ideas. Martin?
- Companion conversions / UI for this feature
- R+1 when configuring Rudder Trim on phase 1 should be impossible
[Taranis] Issue #554 - Default is now :0 (all trims linked to the
default phase)
[Taranis] Issue #554 - Bug fixes (radio part)
Font related alignments
[Taranis] Issue #554 - Automatic EEPROM conversions
[Taranis] Issue #554 - Companion part done
[Taranis] Issue #554 - Constant used instead of hardcoded value
EXPO_LINE_WEIGHT_POS shifted to fit into copy-box
Merge remote-tracking branch 'origin/next' into
bsongis/Issue554_trims_relative_default

Conflicts:
	companion/src/eeprominterface.h
	companion/src/firmwares/er9x/er9xinterface.cpp
	companion/src/firmwares/ersky9x/ersky9xinterface.cpp
Avoid recursive calls to getTrimValue
VC doesn't like binary constants
Merge remote-tracking branch 'origin/next' into
bsongis/Issue554_trims_relative_default

Conflicts:
	radio/src/gui/menu_model.cpp
[Taranis] Issue #592 - Sticky switches