MAVLink app: Default to MISSION, not MISSION_INT
MAVLink app: Default to MISSION, not MISSION_INT

In order to ensure correct transmission the mission system needs to default to the legacy protocol and switch to the new implementation when these conditions are met:
  * If the GCS sends a MISSION_REQUEST_INT - it will do this based on the AUTOPILOT_VERSION flag indicating int mission support
  * If the autopilot sends a MISSION_REQUEST and has the AUTOPILOT_VERSION flag for 2.0 set, the GCS should NACK it, which will make the autopilot retry a MISSION_REQUEST_INT
  * If the autopilot sends a MISSION_REQUEST_INT and the GCS does not support it, the GCS will ignore and time out. The autopilot could retry now opportunistically with the old protocol, but this is not great for lossy links.
  * If the GCS sends a MISSION_ITEM_INT - this is a fallback

mcgill-robotics/Firmware,PX4/Firmware,mcgill-robotics/Firmware,dagar/Firmware,PX4/Firmware,krbeverx/Firmware,jlecoeur/Firmware,Aerotenna/Firmware,jlecoeur/Firmware,Aerotenna/Firmware,krbeverx/Firmware,dagar/Firmware,jlecoeur/Firmware,mje-nz/PX4-Firmware,mcgill-robotics/Firmware,Aerotenna/Firmware,mcgill-robotics/Firmware,PX4/Firmware,dagar/Firmware,PX4/Firmware,PX4/Firmware,mcgill-robotics/Firmware,acfloria/Firmware,krbeverx/Firmware,PX4/Firmware,jlecoeur/Firmware,jlecoeur/Firmware,acfloria/Firmware,acfloria/Firmware,acfloria/Firmware,jlecoeur/Firmware,Aerotenna/Firmware,dagar/Firmware,krbeverx/Firmware,acfloria/Firmware,dagar/Firmware,krbeverx/Firmware,mje-nz/PX4-Firmware,dagar/Firmware,mcgill-robotics/Firmware,dagar/Firmware,PX4/Firmware,jlecoeur/Firmware,Aerotenna/Firmware,mje-nz/PX4-Firmware,jlecoeur/Firmware,krbeverx/Firmware,mje-nz/PX4-Firmware,mje-nz/PX4-Firmware,Aerotenna/Firmware,krbeverx/Firmware,mcgill-robotics/Firmware,acfloria/Firmware,acfloria/Firmware,mje-nz/PX4-Firmware,Aerotenna/Firmware,mje-nz/PX4-Firmware