Use ConditionSeverityError only if the error is non-transient

[sedefsavas]

Some conditions are set incorrectly to false with error severity, even if the failures are transient.
Transient failures mostly happen during the cluster creation, and when AWSCluster conditions are set to false with Error severity, it bubbles up to Cluster Ready() condition with error severity and could be interpreted as an unrecoverable error.

We should set transient errors with Warning severity.

Example (left side is Cluster and right side is AWSCluster):

[k8s-ci-robot]

@sedefsavas: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.