[Experimental] Create desktop target for web app via Electron wrapper

[ajmcquilkin]

Description

This PR is the result of a conversation the Meshtastic Discord (link) around "we need a cross-platform desktop app without significantly increasing maintenance load," which an Electron wrapper of the web client checks off in a lot of ways. This branch and (draft) PR aren't yet in a working state, but I'm publishing this mostly to get feedback on whether this would be an avenue to continue down.

Changes Made

• Adds a new packages/desktop package which wraps a built version of packages/web in an electron app
• Makes translation imports relative, as the built web app code isn't served from the root of the electron ap
• Make URL redirects relative along similar lines (not sure this is needed)
• (Temporarily) disables the Secure Context check on the web app given electron uses the file: transport and not localhost nor https:

Testing Done

None yet, this is experimental

Screenshots (if applicable)

Checklist

• Code follows project style guidelines
• Documentation has been updated or added
• Tests have been added or updated
• All i18n translation labels have been added (read
  CONTRIBUTING_I18N_DEVELOPER_GUIDE.md for more details)

[danditomaso]

Sorry just following up on this now. I think the approach I'll be taking to getting this type of work running is moving a lot of our business logic into an SDK library package, I really want to get to place where you can take our web-client SDK and without a UI actually get up and running and talking to your Meshtastic device. I plan on moving the transports and any other libraries under this yet to be created SDK package. Wanted to see if you felt comfortable marking this as an active PR? Since this is an experiment I think its safe to merge and simply mess with it and see how it can be improved. What are your thoughts on this approach?