fix: add general error boundary on cache routes

[paolapog]

I've found a way to solve #583
Basically was missing a <GeneralErrorBoundary> component with its error handling component because if you were taking the error from the cache routes was resulting in an undefined result.
The error from general error boundary is an object with inside data that contains the error.

Test Plan

1. Login to epic stack with a non-admin user
2. Navigate to ./admin/cache route
3. See the correct error being showed
   

[kentcdodds]

Thanks!