feat: send events related to resource scheduling

[richcooper95]

Summary

In #367 we introduced some events into Kratix. This story is to continue this trend by firing events to the Resource Request when the workloads have been:

• scheduled (un)successfully;
• written (un)successfully to the state store.

These should be very similar to the events in #369, but should be geared towards readability for users of the platform (i.e. focus on what matters to a resource-requester).

Details

We can add an EventRecorder to the reconciler for the WorkPlacementController and the Scheduler, which can then be used to fire events associated with a Resource (see #367 for examples).

Note

NB: We may decide not to do this, since we already fire events when the Resource Request becomes healthy, and that might be sufficient. However, we might want to enable platform engineers to look at a Resource Request to debug scheduling issues, so it may still be useful to record this information via the extra events in this story.