Re-write Kubernetes Condition convention

# Summary
After the last enhancement that was pushed to master where the Condition object was re-written to follow Kubernetes convention. I realized that kubectl can not be used yet with AppSources.

# Motivation
We would like to offer users the ability to use the `kubectl wait --for=condition=` option with appsources.

# Proposal
Re-write the AppSourceCondition based on the pod conditions template and verify that kubectl wait works on it

Locate the AppSourceCondition definition and its current condition serialization, then compare it with the Kubernetes pod conditions template. Verify the resulting AppSource behavior with kubectl wait --for=condition= against an AppSource. Done means AppSources follow the Kubernetes condition convention and kubectl wait works for them.

Written by the indexing model from the issue text.