Add web-serial-polyfill where navigator.serial is not available

[McGiverGim]

Android (and other systems) didn't have the navigator.serial API. This is an effort to replace it with the web-serial-polyfill library, that is a replacement of the other but using the navigator.usb API to connect with the serial device.

NOTE: This has not been tested, I make the PR to try to test it under netlify because navigator.usb needs a secure-context.

[netlify]

✅ Deploy Preview for origin-betaflight-app ready!

Name	Link
🔨 Latest commit	b5bc943
🔍 Latest deploy log	https://app.netlify.com/sites/origin-betaflight-app/deploys/66406bd7520b6b00087be737
😎 Deploy Preview	https://deploy-preview-3948.dev.app.betaflight.com
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sonarcloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Do you want to test this code? Here you have an automated build:
Betaflight-Configurator-Android
Betaflight-Configurator-Linux
Betaflight-Configurator-Windows
Betaflight-Configurator-macOS
WARNING: It may be unstable and result in corrupted configurations or data loss. Use only for testing!

[McGiverGim]

It seems to be an issue to access the USB api in Android. A lot of phones come with preinstalled USB drivers. When you connect the device, the driver "takes the control", so when the navigator.usb api tries to connect it can't. The navigator.api does not have any method to disconnect/force this access as far as I know.

Some phones like pixel 2 can work, and others like pixel 6 or 7 don't. I doubt we have in PWA another way to access this devices, without wrapping the PWA into an app that can do this usb disconnect before, some easier idea?

Confirmed that it works in a Pixel 2:

But this PR is ok, so I think it can be merged. At least it will work for "some users", while we try to find a better solution, that can take time, or Chromium fixes the issue: https://issues.chromium.org/issues/40137537 that I suppose will take a lot more time.