fix: set Ready for resources that miss status.conditions - second attempt

[tomaszkiewicz]

Description of your changes

Fixes #29 @reedjosh

This is a second attempt, that uses function input to specify GVKs that should have forced readiness.

Sample usage:

- functionRef
    name: function-auto-ready
  input:
    apiVersion: auto-ready.fn.crossplane.io/v1beta1
    kind: Input
    forceReady:
    - kind: ProviderConfig # you can also specify apiVersion, but without that it does "magic" to all ProviderConfigs
    - kind: EnvironmentConfig 

I have:

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

[bobh66]

#160 resolved this issue for native kubernetes resources, and there are methods of indicating resource readiness in the composing functions, like the annotation used by function-go-templating