obj persistence: delete objects directly by object ID

Previously, you could only delete objects from flash
if they had been initialized.  This prevented deleting
settings UAVOs for optional modules that were currently
disabled.

Now, you can delete the object from flash directly by
object ID + object instance.  This allows a user to
delete specific settings objects when in BootFault mode
even when the problem module is disabled.
obj persistence: rename UAVObjDelete to UAVObjDeleteByID
Merge pull request #349 from solidgoldbomb/directly-delete-objects

obj persistence: delete objects directly by object ID
added combobox to mixercurve.ui
added condition to show combobox
addUAVObjectoWidgetRlation
call original methods from configTaskWidget
some clealing and added label input source information
cleaning
remove magic values
flyingf3: increase init stack size

FlyingF3 was blowing its init stack.  This leaves us
with at least 64-bytes of margin on the init stack with
a default configuration.
Merge pull request #369 from metropt/custommixFinal

Custommix final
Merge pull request #374 from solidgoldbomb/flyingf3-init-stack

flyingf3: increase init stack size