set Ready condition after running ansible

[d-honeybadger]

Description of your changes

Fixes #228

This sets Ready condition based on the result of an ansiblerun. Ansibleruns can't observed as a typical crossplane external resource, but interpreting the exit code as the availability indicator seems like the next best thing.
I'd also like to extract a better error message than just exit code X (which is the error message), but that requires parsing ansible logs and there's some yak shaving to do to make that possible.

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

1. Deploy modified version of provider-ansible in a k8s cluster (make local.xpkg.deploy.provider.provider-ansible)
2. Create an ansiblerun w/ the default run policy ObserveAndDelete. Here's my example:

apiVersion: ansible.crossplane.io/v1alpha1
kind: AnsibleRun
metadata:
  annotations:
  name: test-run
spec:
  forProvider:
    executableInventory: false
    inventoryInline: |
      cluster:
        hosts:
          test:
            ansible_host: <VM IP>
    playbookInline: |
      - hosts: cluster
        tasks:
        - file:
            path: /test
            owner: root
            group: root
            mode: '0600'
            state: touch
    vars:
      ansible_ssh_private_key_file: ./ssh_id
  providerConfigRef:
    name: test-config

3. Observe the status of the run become

  - lastTransitionTime: "2024-01-18T21:23:12Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2024-01-18T21:23:19Z"
    reason: Available
    status: "True"
    type: Ready

4. Change the playbook to introduce a failure. For example,

 playbookInline: |
      - hosts: cluster
        tasks:
        - file:
            path: /test2
            state: file

5. Observe the status of the run become

   - lastTransitionTime: "2024-01-18T22:05:19Z"
    message: exit status 2
    reason: Unavailable
    status: "False"
    type: Ready
  - lastTransitionTime: "2024-01-18T22:05:19Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced

While ReconcileSuccess is true simply b/c lastappliedconfiguration matches the current spec, the resource is still marked as unavailable, as expected.

6. Repeat the process with ansible.crossplane.io/runPolicy: CheckWhenObserve annotation. It actually will be failing b/c of
   CheckWhenObserve mode broken b/c ansible logs are not valid json #290, but at least make sure no other issues were introduced.

[morningspace]

@d-honeybadger The CI lint is failing. Could you please fix it? The other changes look good to me!

[d-honeybadger]

@d-honeybadger The CI lint is failing. Could you please fix it? The other changes look good to me!

Oops fixed that, thank you!

[d-honeybadger]

@morningspace ready for re-review 🙏

[morningspace]

LGTM