Failsafe: make the safety margin 100 us

This is a bit tight on the range of trims people might use
so I don't really like it.  I think we discussed applying
this only to throttle.
ManualControl: remove unused defines
manualcontrol: always validate flightmode channel when it is configured

Previous code would skip validating the flightmode when FlightModeNumber
was set to 1.  Whenever a flightmode channel is configured, it should
be validated so that it can consistently be used to detect a disconnected
transmitter.

Signed-off-by: James Cotton <peabody124@gmail.com>
Transmitter: allow channel specific valid input ranges

Now throttle uses 100 us to allow Frksy users to get a legitimate failsafe
and other channels remain at 250 microseconds.
Transmitter: separate checking flight mode configuration and validity

Checking for a valid flight mode input needs to run through the hysteresis
loop with the other inputs.  The previous commit had added it but put it in
the configuration loop which means any glitches would instantly trigger
failsafe rather than wait 100 ms.
pios usb: small code cleanup
discoveryf4: add telemetry option to main port
discoveryf4: removed duplicate defines in FreeRTOSConfig.h
discoveryf4: removed total heap size in FreeRTOSConfig.h
discoveryf4: set configCPU_CLOCK_HZ to SYSCLK_FREQ in FreeRTOSConfig.h
DefaultHwSettings: fix layout after module merge
UAVObjectManager: fix crash when sending data from category

Categories when selected allowed you to click send or save which
resulted in a crash.  This disables the buttons when they are when
categories are selected.  This required creating a new
CategoryTreeItem class to detect this.
Merge pull request #644 from peabody124/failsafe_window

Failsafe: make the safety margin 100 us
F4 USB HID and CDC: fixed interface deinit to reset device state
Stabilization: fix bug that made autotuning unresponsive

When introducing the trimmed setpoints in #430 the default behavior became
to ignore inputs.  This is obviously inconsistent with the old code which
by default took the inputs from StabilizationDesired unless explicitly
overriden.  This restores the previous default behavior and keeps the
exceptions for weak leveling and stabilizationplus mode.
Merge pull request #684 from peabody124/stabilization_fix

Stabilization: fix bug that made autotuning unresponsive
Merge pull request #681 from lilvinz/f4_usb_fix

F4 USB HID and CDC: fixed interface deinit to reset device state
Sensors: sanitize baro before setting UAVO

Sometimes right at startup there seems to be an occasional
NAN in the altitude which can poison everything else.  I
considered fixing this in the MS5611 driver but it seems
reasonable to check before setting the UAVO regardless of
whether the MS5611 should have produced NAN.
Merge pull request #685 from peabody124/baro_sanitize

Sensors: sanitize baro before setting UAVO
Merge pull request #676 from lilvinz/usb_cleanup

pios usb: small code cleanup