[Extensibility] Catch and handle when an extension fails to load

Current Behavior

Here is an example an extension failing to load. This error is from the console of a user's web browser:

 [Error] Extension Error: Error: HTTP Error Response: 404 Not Found (/api/provider/extension/provider/navigator/meshmap/collaboratorsPlugin.js)

The current behavior is that the user is perpetually stuck on a loading screen. The user has no indication as to whether or not the plug-in is still loading or if it has failed or how much longer it might take to load.

Desired Behavior

This failure to load should be captured, and the Sistent feedback component presented to the user for ease of reporting of the issue.

Implementation

1. Use Sistent feedback component.
2. Use existing Error Boundary component.
3. User should be redirected to the dashboard upon submission of the feedback.
4. While Meshery UI plays a role in catching the air and in redirecting the user, ultimately, Meshery Server is in control of the actual redirect.

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 📺 Self-paced Contributor Trainings
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack