fix(gatsby): minor refactor of console functions

[leonlafa]

Description

To discourage the use of console.log in our plugins so everything that is called directly on console functions ends up being a regular log.

Related Issues

fixes issue #14834

[leonlafa]

Could someone review the changes?
Once done I'll go ahead and clean up all of the instances of console.log usage with reporter.log()

[DSchau]

Unsure of the original reason for this PR -- so tagging in @sidharthachatterjee to provide some context. Thanks!

[wardpeet]

Looks awesome!, this is great thanks!

[gatsbot]

Holy buckets, @leonlafa — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

[leonlafa]

@wardpeet My next task is to go through and change all the console function instances and refactor for reporter.log functions as suggested by @sidharthachatterjee

What's the best practice?

Should I raise a new issue myself or should I let one of the members raise it and then I'll start work on it?

[sidharthachatterjee]

Thanks for the ping @DSchau and thank you for reviewing @wardpeet 🙌

@leonlafa Feel free to open an issue and start working on it! Thank you 💜 💪