fix: standardize error logs to use %e token

[gulshanpr]

Title

Standardize error logs to use %e token

Description

Replaced old %s/%o error logging with the %e token across the codebase for consistency.

Issue #3161

Notes & open questions

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[seetadev]

@gulshanpr: Hi Gulshan. Wish to ask if the PR has been tested locally.

Please attend the upcoming js-libp2p calls on Wednesday. We will work out a clear plan on ensuring we are meeting the requisite needs in reference to js-libp2p. CCing @dhuseby.

[gulshanpr]

so to prove this PR, do i need to add test along with it or running npm run test locally works?

[achingbrain]

Thanks for opening this PR.

As it just changes log lines there's no need to add a test.

Unfortunately there have been disruptive changes in main as part of prep for the v3 release - please can you fix the merge conflicts here.

[gulshanpr]

hi @achingbrain i've fixed the merge conflicts, can you review it now?

[achingbrain]

I have done a partial review but this PR is full of merge conflicts that have not been resolved and instead added as-is to the PR.

I cannot continue this review until this PR will apply to main cleanly.

General comments are:

1. Where there was previously this.log(err), instead of changing it to this.log('%e', err), add some more context, e.g. this.log('error while Xing the Y - %e', err).
2. Do not change the casing of log messages, in this codebase error logging is lowercase and messages passed to Error instances is sentence case

[gulshanpr]

Hey @achingbrain,
I fixed all the requested changes and made sure,

• casing is correct
• context in log.error()
• and no more merge conflicts

could you pls review it now