Prioritize critical resource annotation updates over status updates

[ulucinar]

Description of your changes

Recently with #263, we have deprioritized critical annotation updates wrt status updates. However, we would like to have them prioritized over all others.

I have:

• [x] Read and followed Crossplane's contribution process.
• [x] 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

Tested against provider-jet-azure by provisioning a resource with it.