Unknown status shown when reconciling (with bad config)

Summary

The Flux reconciliation status on the Environment cluster UI integration shows "Unknown" status when Flux is reconciling a badly configured deployment.

Steps to reproduce

1. Set up a working Flux deployment
2. Set up a tool to check the Flux reconciliation status (e.g. weave gitops)
3. Check that the environment shows a green / Reconciled Flux status
4. Change the Flux deployment to point to a not-existing image

Example Project

What is the current bug behavior?

The cluster UI shows "Unknown" status

What is the expected correct behavior?

The cluster UI should show "Reconciling" status

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Add a new case for sync status badge to handle the reconciliation with a non-existent image. Search for a status with fields:

type: 'Ready'
status: 'Unknown'
reason: 'Progressing'
message: 'Reconciliation in progress'

as stated in the HelmReleaseProgressing method.