Massive Refactor - Custom Action Feature Types

[Nerwyn]

Is your feature request related to a problem? Please describe.
Only one slider and touchpad are allowed per remote. There are good use cases for multiple touchpads and sliders.

Describe the solution you'd like

• All custom actions should get a type field with possible values button, slider, or touchpad. This should allow for the creation of multiple sliders and touchpads.
• Deprecated field logic for touchpad and slider fields outside of custom actions, like touchpad style and slider ID.
• Would be a good opportunity to add labels and icons to all features.
• Need to move all internal value logic from slider to base class, like it is in service call tile feature.
• Touchpad actions (center, up, down, left, right) would have to be redefined within the touchpad custom action rather than using button actions
  • Except for default touchpad option which would use button actions.

Describe alternatives you've considered
Multiple remote cards in a stack, but this doesn't work for multiple of the same element in a row.

Additional context
I should be able to reuse and unify logic from/with service-call-tile-feature.