fix: set Ready for resources that miss status.conditions

[tomaszkiewicz]

Description of your changes

Fixes #29

I have:

• Read and followed Crossplane's contribution process.
• Added or updated unit tests for my change.

[phisco]

A resource could just have no conditions set yet afaict, so this could mean we mark as ready something that isn't actually ready

[tomaszkiewicz]

Do you have any suggestions on how to handle cases like ProviderConfigs or EnvironmentConfigs which don't set conditions at all?

Ofz we can create a list of these resources, but it's not that flexible and required configuration by the user or (worse) in the code...