feat: Set status Git/BucketStateStores

[aclevername]

Context

Users would like to have feedback after they set up their State Store.

Update Git/BucketStateStores status, logs, and publish events to indicate wether it can successfully authenticate, and give reasonable errors back.

[ChunyiLyu]

Update the issue to include publishing events, and only for State store.

Similar issue for Destination #330

[ChunyiLyu]

Closing this one because:

1. our set up requires people to create a StateStore and a Destination referencing that StateStore at the same time
2. Destination at creation writes canary files to the StateStore while as StateStore creation does not connect to the StateStore

So we believe setting status in Destination will provide enough feedback to our users. Therefore picking up #330 and closing this issue.

[kirederik]

In #330 we introduced Destination status. I think we should still implement State Store status for the following scenario:

1. A secret is created
2. A state store is created referencing the secret
3. A destination is created referencing the state store. At this stage, the destination status is correctly set to Ready.
4. User updates the secret; it's now wrong

Ideally that should trigger a reconciliation of the state store, and its status should now be "not ready". That, in turn, is already set to trigger a reconciliation of the destination -- which would update the destination status accordingly.

i suggest we reopen and implement this

@ChunyiLyu @catmo-syntasso wdyt?