fix: start condition check for deployment with the assumption that it is not available, fixes RHOAIENG-9184

[dhirajsb]

Description

Start by assuming that DeploymentAvailable condition is missing/not available, i.e. only set MR status to available when deployment is actually available. This can happen when the Deployment is initialized in K8s but without any of it's conditions set. Fixes RHOAIENG-9184

How Has This Been Tested?

Tested locally by waiting for availability right away by using the command:

kubectl apply -k config/samples/postgres/; kubectl wait --for=condition=Available=true modelregistries/modelregistry-sample --timeout=5m

Merge criteria:

• [X] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
• [X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• [X] The developer has manually tested the changes and verified that the changes work

[dhirajsb]

Ah, need to fix the integration test, since deployment status will never be true in setup-env test env.