use ophyd async logger for logging.debug statements

[rerpha]

in an interactive shell we found we got a global logging handler added after a PV failed to connect.

We found these logging.debug statements which use the "simple"/global logging API which is not recommended as per: https://docs.python.org/3/library/logging.html#logging.debug

where it mentions this:

The only difference is that if the root logger has no handlers, then basicConfig() is called, prior to calling debug on the root logger.
For very short scripts or quick demonstrations of logging facilities, debug and the other module-level functions may be convenient. However, most programs will want to carefully and explicitly control the logging configuration, and should therefore prefer creating a module-level logger and calling Logger.debug() (or other level-specific methods) on it, as described at the beginnning of this documentation.

This PR gets the ophyd-async logger and uses it instead of the global functions.

[Tom-Willemsen]

• Looks like we missed one in https://github.com/bluesky/ophyd-async/blob/main/src/ophyd_async/core/_utils.py#L117 (detected via ruff rule LOG015) - probably because we missed searching for exception.
• Might as well fix or add a noqa to the one in .github\pages\make_switcher.py while we're here?
• Maybe we could consider selecting ruff rule LOG015 to make this a lint error?