bug: bitswap log severity as ERROR is confusing for users

[jcstein]

When running light node on v0.18.2-mocha, I observe a flood of logs:

2024-10-08T14:38:50.290-0400	ERROR	shwap/bitswap	bitswap/block_fetch.go:190hasher: no unmarshallers registered for bagipaamr6aaqyaaaaaaaak6uuyaauaaq

While the log can be ignored and is non-critical, it is confusing and worrisome to users who see "ERROR" repeatedly in their logs.

The error message should say "INFO" if this is not in fact an "ERROR"

errorlogs.mp4

[Wondertan]

The good news are. I've been running a version of node over the weekend with none of those logs addressing the root issue. We can expect it to come around next week.

[Wondertan]

There are duplicate messages being requested and every duplicate spawns a log.