Blueprints: Improve error handling for deeplink failures

[ivan-ottinger]

Related issues

• Resolves STU-1209

Proposed Changes

• add user-friendly error messages when Blueprint deeplink open fails
• add related tests

Before	After

Testing Instructions

1. Check out the PR branch and build the app with npm install && npm start.
2. Try opening first two broken Blueprint deeplinks at https://jsbin.com/kulaqijega/1/edit?html,css,output.
3. Both should open an user-friendly error message with option to see the exact error message in the Studio app logs.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[epeicher]

Thanks @ivan-ottinger for improving this! I have tested it, and I can see the new error messages.

Although I'm not sure I like the double Failed to load Blueprint and then The Blueprint could not be loaded. and not displaying the returned error message. I would be interested in others' views on those

Network Error	Invalid Blueprint error

[katinthehatsite]

I agree with Roberto's assessment regarding the wording being repetitive. Maybe The Blueprint could not be loaded could be skipped altogether.

[katinthehatsite]

Although I'm not sure I like the double Failed to load Blueprint and then The Blueprint could not be loaded. and not displaying the returned error message. I would be interested in others' views on those

I agree with this assessment, although I think we don't necessarily need the exact error message in this window as as it will be in the logs as well. We should definitely adjust the repetitive wording though.