error boundaries, fallbacks, loading states

[laholstege]

          even tho above we redirect them if they're not a cluster admin, i still like to handle it when returning what to render to cover our bases. something like 

if(isClusterAdmin === false) {
 return <NotAuthorized />
 }

and same goes with any other potential error states. you have your loading states covered, but what happens if fetching the order fails, what renders? it'll be Loading... forever. i'll add the error handling pattern, but i just wanted to point out it's good practice to think about how errors effect both your event handlers/API calls, and what you render

Originally posted by @laholstege in #321 (comment)

[laholstege]

#435 adds error boundaries. still need to cover 404s, etc