Test/browser setup

[PixnBits]

I noticed there were no automated tests. I'd wager it is probably effective to start with browser testing than unit tests in the event of some implementation refactoring. This is a setup with Playwright, with the start of some tests. I can continue to expand the tests if this approach is desirable, or change course based on maintainer feedback 👍

[PixnBits]

I did have the image snapshots added

$ git status
...
new file:   tests/example.spec.ts-snapshots/Prompts-adding-a-new-connection-as-the-call-to-action-when-there-are-no-devices-1-chromium-linux.png
new file:   tests/example.spec.ts-snapshots/Shows-the-protocols-as-the-first-step-of-adding-a-device-1-chromium-linux.png
new file:   tests/example.spec.ts-snapshots/connect-over-http-chromium-linux.png
new file:   tests/example.spec.ts-snapshots/connect-over-serial-chromium-linux.png

but when pushing to my fork I got the message

$ git push --set-upstream origin test/browser-setup 
batch response: @PixnBits can not upload new objects to public fork PixnBits/meshtastic-web                                                                                                                                         
error: failed to push some refs to 'github.com:PixnBits/meshtastic-web.git'

When looking for the cause or a needed setting I found

Git LFS on github.com does not currently support pushing LFS objects to public forks.

git-lfs/git-lfs#1906 (comment)

The image snapshots could be useful for documentation purposes in addition to quick visual change checks, but with this restriction by GitHub could be an impediment to contributors?

[PixnBits]

Before moving this PR to a ready state we might need to think through the impact of GitHub's image storage on contributions?
#205 (comment)

I'm in the Meshtastic Discord "server" if that helps \m/

[PixnBits]

I'll remove this example file before moving the PR to ready for review 🫡