Consistent Logging

[devigned]

/kind feature

I've found there are 3 ways we are currently logging.

1. directly via klog
2. via the logger on scopes
3. via the span logger

We should have a single consistent pattern for logging to improve the consistency of the code, but more so, to improve the logging experience for the operator of CAPZ.

[Before submitting an issue, have you checked the Troubleshooting Guide?]

What did you expect to happen:
I'd like to see that we consistently use the span logger, so that spans will be sent to both STDOUT, but also as events on our distributed traces spans. The span logger is directly tied to the context. In funcs where there is no context, we should provide the logger or the context as a argument.