Set Paused condition to align with new CAPI recommendation

[nojnhuh]

/kind feature

Describe the solution you'd like

Fulfill CAPI's new recommendation that providers set a Paused condition on resources as described by kubernetes-sigs/cluster-api#10519.

Anything else you would like to add:

Ensure that a Paused: false condition doesn't factor into the general assumption that all conditions must be true in order for Ready to become true.

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[jackfrancis]

/assign @nawazkh

cc @mbrow137

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale