Handle connection errors on environment's prometheus clients properly

We had an issue with a user being unable to load the environments page due to 500 erros. We found this sentry error that pointed at an authentication error with the external_url provided by the user for the environment. Given that such problems are previsible we should consider returning a relevant error to the user instead of failing with a 500.