Consider using metav1.Condition instead of own condition structs

### Requirement

Use the default `metav1.Condition` as conditions on Camel K custom resources.

### Problem

The conditions used in the Camel K custom resources usually are structs that alias to strings.

Instead of this we could try to just reuse `metav1.Condition`, which would allow to manipulate conditions using some [k8s utilities](https://github.com/kubernetes/apimachinery/blob/master/pkg/api/meta/conditions.go).

The downside is that we won't have the specific condition type, but given 99% of the time is just an alias to strings and there are no real enums in go, I don't see anymore a very strong benefit.

### Proposal

_No response_

### Open questions

_No response_

Start by locating the Camel K custom resource condition structs and the code that reads or updates their conditions. Compare those uses with metav1.Condition and the Kubernetes conditions utilities; done means affected custom resources consistently use the default condition type and relevant tests pass.

Written by the indexing model from the issue text.