feat: add error boundary

[danditomaso]

• Add Error Boundary throughout the app to prevent unhandled errors from causing the application to crash. Due to how each page is wrapped, the error will be caught at the page level leaving the remainder of the application functional.

• Created a fallback Component which displays a helpful message to the user about what occurred, and a way to file a github issue or navigate back to the root of the application.

• Create a reusable Heading component that supports dynamic heading levels (h1-h5) through the as prop, this enables enabling consistent typography across the application, removed individual H1-H5 components updating references were required.

• Create a reusable newGithubIssueUrl utility function to generate a properly formatted URL for creating new GitHub issues. It provides a type-safe and flexible way to construct issue URLs with various parameters like title, body, labels, and assignees.

It supports the following parameters:
Title and body text
Labels
Issue templates
User assignments
Custom text fields by id

All fields except user and repo are optional.

Example Usage:

newGithubIssueUrl({
  user: 'meshtastic',
  repo: 'web',
  title: 'Bug: Login not working',
  template: 'bug.yml',
  labels: ['bug', 'high-priority'],
  assignee: 'developer-name',
  body: 'Description of the issue...'
  logs: 'Relevant logs'
});

[KomelT]

There should be page scroll bar when Error details is overflowing.

Currently you can't see whole error detail.

[KomelT]

This disconnect returns you to the "New Connection" page. I think it would be better if it would put you to "Connected Devices", so it doesn't disconnect you.

[danditomaso]

That makes sense, but what if the issue/error is on the dashboard? Also the landing page when you first connect is the Messages screen, which I wouldn't want to redirect users to, in order to avoid some kind of error loop. I think I need @Hunter275 to make a call on this one.

[Hunter275]

Does the message history disappear if we take them back to the "New Connection" page?

[danditomaso]

The message history would disappear in either case this PR doesn't solve that issue. If they get the white screen its because the app had an error thrown that wasn't being handled, so they would need to reload the app anyway causing all components to remount.

The benefit of this work is that the error is isolated to a single route/page. The cavet is the way the web client is currently built we handle sidebar routing inside each compont instead of a higher level layout wrapper.

This PR provides a graceful fallback component to provide a the user with some feedback about what occurred, where as previously nothing existed before and they were presented with a blank white screen.

Addtionally if they file an issue using the included the Github link, we capture the stack trace as a query param and pass it to github to be included in the bug report (its added to the console log section), so smoother bug filing experience for the user and improved error reporting for us.