fix: hmrClient.logger.debug and hmrClient.logger.error looked different from other HMR logs

[Bryasxin]

fixes #22146

[bluwy]

@sheremet-va It'd be nice to have your input here since you've abstracted the logger before in #15631

The idea makes sense to me to have the logs show consistently, but does this change make sense in general for the logger? And is it normal for hmrLogger.debug to be printed out by default?

[Bryasxin]

I confirmed that hmrClient.logger.debug is printed by default when running bun vite without any extra configuration. So yes, it's currently always active.

Not sure if that's the intended behavior, should it be gated behind a lower log level?

[sheremet-va]

I thought it's not even working by default for the SSR environment 🤔

[sheremet-va]

And is it normal for hmrLogger.debug to be printed out by default?

The implementation just copies how it works in the browser. There it calls console.debug, but I guess it's easier to hide them DevTools. For SSR environment, I am not sure what makes more sense.

[bluwy]

We have debug logging using the DEBUG env var, I think it makes sense so it works that way too if the logs are indeed for debugging and not general logs.

Anyways this is a bigger change, and if this PR looks good to you, then I think we can go with this first. Maybe we want to revisit this before the environment api goes stable.