Handle container registry errors in details pages
🔥 Problem
With !70941 (merged), we provided a way to handle container registry connection errors.
In particular, in the UI, we show a connection error screen.
That screen is handled by the frontend directly. The backend passes a set of boolean flags to say if a connection error is present or not.
Unfortunately, the frontend side doesn't handle well the container image details page with a connection error. When accessed directly (eg. we paste the URL in a browser and load the page), it will show the data coming from rails and add spinners for the data coming from the container registry. Those spinners can't be resolved if there is a connection error and we end up in a partially complete screen. See !70941 (merged).
🚒 Solution
When the booleans flags are set to indicate a connection error, the frontend side should display the connection error screen no matter if we're accessing the container image index page or the container image details page.
In addition, when those flags are set, the frontend side should not fire a GraphQL query to get the data from the container registry side.