MP flight mode is confused by vehicle and components using the same SYSID

If a SToRM32 gimbal is connected to the pixhawk and setup as a component (i.e. uses vehicle's SYSID but separate component id) the mission planner becomes confused about the flight mode (which is sent in the heartbeat). It keeps switching between the vehicle's actual mode and stabilize (because the storm gimbal sets the mode to "0" i guess).

I think the mission planner should just handle a component like a separate vehicle. Luis Alves may have some input on this as well.

Start by reproducing the issue with a SToRM32 gimbal connected to the Pixhawk as a component sharing the vehicle SYSID. Trace how Mission Planner processes heartbeat flight modes from the vehicle and component, then verify that the displayed mode no longer switches incorrectly to Stabilize while the component is present.

Written by the indexing model from the issue text.