chore: do not use f-strings in logging statements

[agriyakhetarpal]

Description

Thanks to the tip in #30 (comment), I enabled a Ruff rule to avoid using f-strings in future logging statements we add: https://docs.astral.sh/ruff/rules/logging-f-string/, and converted the previous ones to comply with the rule. It's not necessarily required, but it's good to enable best practices.

Important

This PR should be merged with a merge commit, not squashed.

[hoodmane]

Thanks for doing this chore @agriyakhetarpal!

[agriyakhetarpal]

Thanks for reviewing it!

[ryanking13]

What's this file for?

[agriyakhetarpal]

When we make formatting/style changes in the code that are not useful for the git blame, we can ignore the commits (revisions) in which the changes were made in the relevant files to keep their history clean.

More on this here: https://graphite.dev/guides/git-blame-ignore-revs

https://github.com/orgs/community/discussions/5033

[agriyakhetarpal]

Now that I fixed it – if you check any of the files, say, main/pyodide_build/buildall.py (blame), it wouldn't show the formatting change in the history (by default).

[agriyakhetarpal]

Also, oops, I was using GitHub through my phone and I squash merged it instead of creating a merge commit 🤦🏻 Let me fix this in a new PR.

[agriyakhetarpal]

Fixed this in the main branch because we would have had to remove the squashed commit anyway. I had to force push; sorry for the inconvenience!