Feat: Interopathon Support (did:peer:4 & Empty Messages)

[TheTechmage]

In preparation for the DIDComm V2 Interopathon, these changes are bringing us closer to in-line with the requirements by adding support for did:peer:4 (we now generate and can resolve those DIDs) and empty messages

[dbluhm]

Several console logs that you might consider cleaning up or removing or logging to the "official" log that is displayed on the page

[TheTechmage]

Unfortunately, updating those log lines to clarify and adding some to the logger marked your review as stale.
To clarify: Some logs are output to console.log because the logger.log expects strings only. Even if JSON and objects get stringified, having the text in the console log as "not an object" makes the object significantly more difficult to quickly parse what was contained within the message. A couple of the things that are being logged are also logged where the logger doesn't exist, such as: within the web worker.

One of these days, I think it would be worth-while to expand the logger to accept any[] instead of string[], and have the log renderer display "pretty" JSON output that is collapsible. But that is out-of-scope for this PR.