Fix hydration error on ResourcePage

This was fixed by using responseContext to determine whether or not to
render an `AccessDeniedError`.

This feels fairly fragile, but not sure how it can be improved as long
as errors aren't passed with the graphql cache from server to client.

src/containers/ResourcePage/ResourcePage.tsx

@@ -102,12 +102,12 @@ const ResourcePage = () => {
   }
 
   const accessDeniedErrors = findAccessDeniedErrors(error);
-  if (accessDeniedErrors) {
+  if (accessDeniedErrors || responseContext?.isAccessDeniedError()) {
     const nonRecoverableError = accessDeniedErrors.some(
       (e) => !e.path?.includes("coreResources") && !e.path?.includes("supplementaryResources"),
     );
 
-    if (nonRecoverableError) {
+    if (nonRecoverableError || responseContext?.isAccessDeniedError()) {
       return <AccessDeniedPage />;
     }
   }