Before reinstating the MSP sends on TLM connection, maybe review this: #1812 - I did not agree with how this was resolved at the time.

It can fail the "principle of least astonishment" if the VTX is being configured via Betaflight, eg I use my 6-way switch to control the VTX tx power setting. Then suddenly in mid-flight, TLM disconnects and reconnects, and ELRS reconfigured the VTX in-flight which can have very bad consequences. I don't know if this is why it was taken out, but reconfiguring the VTX in-flight is, I think, almost always a bad idea.

There was a resolution in #1812 that says if you are using any other method to set the VTX power level, then you should set the VTX admin power level to - so it is then NOT sent to the FC/VTX.

I'm tagging myself onto this PR because the added VtxTriggerSend() breaks SPI RXs, which connect, then get a VTX update and forced save, which paused the FC/RX and drops the connection. It immediately reconnects (many times without even without there being any indication on the handset) which causes another VtxTriggerSend() and the cycle repeats indefinitely.

Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:500
TLM crc error
UART STATS Bad:Good = 0:501
got downlink conn
UART STATS Bad:Good = 0:500
Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:500
UART STATS Bad:Good = 0:501
got downlink conn
UART STATS Bad:Good = 0:500
Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:500
UART STATS Bad:Good = 0:501
got downlink conn
UART STATS Bad:Good = 0:500
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:500
UART STATS Bad:Good = 0:501
got downlink conn
UART STATS Bad:Good = 0:500
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:500
UART STATS Bad:Good = 0:501
got downlink conn
UART STATS Bad:Good = 0:500
Sending VtxConfig
$X<Y ▒Sending VtxConfig
$X<Y ▒UART STATS Bad:Good = 0:501
Sending VtxConfig
$X<Y

This solution should be examined as it can also affect normal RX users I think if the timing works out just right, but I'll get back to it at a later time.