Drop MTK GPS

[JulioCesarMatias]

iNavFlight/inav#8084

[Jetrell]

@JulioCesarMatias Can I get you to look at the order these are printed in the Configurator?

With this build and its firmware, UBLOX7 entered into the CLI, appears as DJI NAZA.
And UBLOX7 entered into the GPS tab, shows up as MSP in the CLI.
While NMEA and UBLOX can't be loaded into the CLI, and cause a lockup.

[JulioCesarMatias]

@JulioCesarMatias Can I get you to look at the order these are printed in the Configurator?

With this build and its firmware, UBLOX7 entered into the CLI, appears as DJI NAZA. And UBLOX7 entered into the GPS tab, shows up as MSP in the CLI. While NMEA and UBLOX can't be loaded into the CLI, and cause a lockup.

It wasn't this PR that caused this problem, in fact it wasn't any PR at all. What happened was a break in the Master branch.

The word "UNUSED" was removed by me through this PR >> iNavFlight/inav@2d3f772

The word "MTK" was removed by me through this PR >> iNavFlight/inav@7208a78

In iNav-Configurator master "UNUSED" and "MTK" does not exist more >>

inav-configurator/js/fc.js

Line 595 in 09f40d9

getGpsProtocols: function () {

I believe that Settings.md somehow failed, and was not generated correctly.

[stronnag]

master Configurator needs to catch up with #8144

# version 
# INAV/WINGFC 6.0.0 Jun 26 2022 / 11:36:32 (7abe07e9)
# GCC-12.1.0

# get gps_pr
gps_provider = UBLOX7
Allowed values: NMEA, UBLOX, UBLOX7, MSP