fix: Don't mark CRD degraded while 'Installing'

[kbweave]

This fix updates the CRD health check to be aware of the "not Estabilshed yet but currently Installing" state.

During syncs of existing applications we were getting notifications about degraded applications but the state was very fleeting. We'd check the UI and everything was synced and healthy. After combing the logs and doing some troubleshooting, we found that the CRD health check was causing the ArgoApp to report degraded for a short amount of time when the application was applying new CRDs during its sync.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Title of the PR
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[bunnyshell]

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🔵 /bns:start to start the environment
• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to remove the environment