Virtual registry upstream connection status

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Design proposal:

• Updated design: #560911[RegistryDetail.png]
• Original design: #493842[Registry-with-upstream.png] (comment 2379022369)

🔥 Problem statement

Currently when there is a network issue with an upstream, we don't surface that situation. With several upstreams to 🤹 with, it can be challenging to understand the upstream health.

🚒 Solution

We should record when an upstream can't be accessed due to a network error (not having a requested file is not an error).

Let's start simple with:

• Update the upstream model with the last error (fields last_error and last_error_at). last_error should be filled with a clear explanation of what has been accessed (relative path) and what happened.
• Reset these fields when we successfully access an upstream. ⚠️ Do it in a delayed way. DO NOT write to upstream when we try to pull files from it (eg. keep that web request as a replica only situation).
• Surface these fields in the upstream details REST api