Expose the logging functions to client-side extensions and automatically account for the value of isDebug

[ShyamGadde]

Summary

Fixes #1886

Relevant technical choices

• Introduced a logger object that encapsulates log, info, warn, and error methods.
• The logging functions automatically respect the value of isDebug coming from WP_DEBUG in PHP.
• Exposed logging functions to client-side extensions' initialize() and finalize() functions.
• Errors (error()) always log regardless of isDebug, since most existing calls didn't check for it.

[ShyamGadde]

Note about error logging: I noticed that in 5 out of 7 usages, the error function was called without checking isDebug first. It seemed intentional that errors should always be shown, so I've maintained this behavior in the logger implementation. The remaining two cases still explicitly check isDebug before calling error(). Let me know if we should standardize this behavior differently.

[westonruter]

Yeah, good call. This probably makes sense to log out even if not isDebug.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ShyamGadde <shyamgadde@git.wordpress.org>
Co-authored-by: westonruter <westonruter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[westonruter]

Looks good!

If Embed Optimizer and Image Prioritizer are updated without Optimization Detective:

Where the log entries from Embed Optimizer and Image Prioritizer lack the prefixes as expected as a fallback for Optimization Detective not being updated yet.