feat(web): Add Web Serial and Bluetooth API support

[MakeSomeFakeNews]

Summary

This PR adds native Web support to INAV Configurator, enabling it to run in browsers using modern web APIs while maintaining full Electron desktop compatibility.

Changes

• Web Serial API Support: Direct serial port connection from the browser
• Web Bluetooth API Support: BLE device connection from the browser
• Dual Environment Support: Works in both Electron (desktop) and web browsers
• Smart Connection Interface: Automatically detects and enables available connection methods
• Web-Optimized Vite Config: Build configuration specifically tuned for web deployment
• Updated Backend Logic: Connection handling supports both traditional and web-based APIs

Technical Details

• Uses native Web Serial API (Chrome, Edge, Opera)
• Uses native Web Bluetooth API for wireless connectivity
• Maintains backward compatibility with existing Electron features
• Optimized Rollup plugin configuration to prevent asset parsing warnings
• Proper handling of connection types based on environment

Browser Support

• Chrome/Edge/Opera (Web Serial API)
• Chrome/Edge (Web Bluetooth API)
• Firefox (via polyfills in future)

Backward Compatibility

• All existing Electron features remain intact
• No breaking changes to existing codebase
• Web features are additive, not replacement

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change because it should never be included in any release, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

💡 Need a hand with PR review? Try Gitar by Sonar!

[sensei-hacker]

Do you have a copy up where it can be tested?

Here are some references of recent similar work. We may want to compare and contrast and merge ideas together to come up with the final combined version.

@Scavanger 's similar work:
#2448
Testable at https://inav-configurator.pages.dev/

And the one by @RomanLut :
#2597
Testable at https://romanlut.github.io/inav-configurator/

and @ramkrishna757575 started a version
#2693

one by MakeSomeFakeNews:
#2687

While @Bingo2023 made an Android app:
https://github.com/Bingo2023/inav-configurator-android
Discussion here:
iNavFlight/inav#11711

Overall discussion of the topic here:
#2696

[sensei-hacker]

Just an FYI for contributors: The tentative schedule for INAV 10 is to have a full release in mid December. That means RC2 needs to be in early to mid November, which places INAV 10.0RC1 at September 1. Please plan to have any new features for INAV 10.0 ready for RC1 no later than September 1. After that, 10.1 will follow about six to seven months later.