AP_GPS: drop default GPS lag to 0.1s

[tridge]

this impacts UAVCAN GPS modules, which these days usually have at
least u-blox M8

[khancyr]

on matek M8Q it is 0.11 (MSP backend), on Ublox backend it is at 0.12, now you said 0.1
Shouldn't we harmonized all those ?

[tridge]

Shouldn't we harmonized all those ?

ublox varies with sensor type. 100ms is a compromise when we don't know sensor type. Ideally we would detect the text message from the CAN GPS giving the sensor type and set based on that, but this is a better value than we have now. When we chose 220ms the "normal" GPS was M6 or worse. Lag is a lot better now.

[khancyr]

Ok, no problem. I was just surprised by the differences for the same ublox

[IamPete1]

This broke CI in some odd ways, seems to create a interesting status text race condition.

#19675

[hendjoshsr71]

Specific tests failing are test.Plane.DCMFallback & test.Rover.GripperMission