Chore(Internal): Switch all resources to use status struct with common fields

[Baarsgaard]

Similar to #1765 this is working towards grinding down the differences between the various resources and reconciliation functions.

The goal here is to establish a common set of fields that should always be present on a Status object.
Additional fields can then be added as necessary as seen in the Dashboard status

[weisdd]

@Baarsgaard My concern here is that it's not a 1:1 switch, because some resources do not implement either LastResync (alert groups, contact points, notification policies) or Conditions (datasources). So, I guess we should add the missing logic either in this or a separate PR. WDYT?

[Baarsgaard]

The plan was to discuss what fields should be in the Common status object.
Then once we agree, add them all in this PR since unused fields don't really do any harm.
After that I would refactor each reconciler one at a time.
It aligns well with how @theSuess wanted to do smaller releases previously.