[UX Gap] Error Messages and Troubleshooting

[smeragoel]

This is a tracking issue for UX problems related to error messages and troubleshooting in Nebari.

Summary

Nebari currently surfaces raw or unclear error messages across several parts of the platform. These stack traces / logs that are not user-friendly. Improving error reporting UX will also reduce support overhead, improve onboarding and let users solve common problems independently.

Key Problems

• Raw stack traces
• Lack of actinoable guidance in error messages
• Missing documentation links

Personas Impacted

This impacts primarily end-users.

Proposed Recommendations

• Create user-friendly error display patterns
• Write copy for common errors
• Link errors to docs wherever applicable

[smeragoel]

I'm unable to add issues from the Nebari repo anymore so I'm linking some more issues here, which may be relevant:

1. [ENH] - Nebari CLI should not display a stack trace for expected errors nebari#1946
2. [UX] - SSHing into a server without a server spun starts a server... but which? nebari#1759