`binenv update [-f]` should exit(1) if ANY issue occurs with cache update

When binenv updates it's cache, it continues when an update for the distribution is encountered.

While this feature is quite nice and can be helpful in some situations, we still want to exit(1) when an error occurs. For instance, when creating a cache in GH actions, we do not want to replace a propre cache with a new one where some distributions are missing.
