Clean up error handling

[dgramop]

We need to bubble errors up from drivers all the way up to the UI in a way that gives users some actionable information, and ideally richer UI components (like links to help articles/driver software)

Common errors should have documentation on how to solve them in-app

[dgramop]

• Remove use of anyhow::Error
  • Consolidate construct errors into a construct error struct
  • Perhaps include SeifyError kinds in FutureSDR instead of eagerly coercing them to a string
• Map errors in studio itself
  • Match on errors to produce strings
  • Replace with a UI component built around the error itself, so we can get rich information
  • Phone number/discord link for any errors we don't explicitly document in the UI on how to handle