Update logging for communication

[AE-MS]

Description

I was investigating a customer issue (#2669) and found that some of the existing log statements were a little misleading and also that we would benefit from a bit more logging, particularly around message passing/communications.

Main changes in the PR:

Adjust a potentially confusing log statement and add a new log statement when sending a message response to a child window (e.g., the authentication pop-up)

Validation

Validation performed:

1. Ensure all existing tests passed
2. Ensured that child window/auth window scenarios continue to work and new logging is seen with expected information (when logging is turned on):

common.js:1 teamsJs:communication:handleIncomingMessageFromChild (2025-01-17T00:35:55.823Z): Handler called in response to message c9ea3b32-2f2a-4d61-905d-c6523eea3d1e (legacy id: 0) from child. Returning response from handler to child, action: initialize. [047ae9b5-524f-4ce7-b3bb-fd2232c565f2] +0ms
...
common.js:1 teamsJs:communication:handleIncomingMessageFromChild (2025-01-17T00:35:55.835Z): No handler for message 1d3fce2d-085d-4c50-8fce-5036361a9d55 (legacy id: 1) from child found; relaying message on to parent, action: getContext. Relayed message will have a new id. [047ae9b5-524f-4ce7-b3bb-fd2232c565f2] +12ms
...
common.js:1 teamsJs:communication:handleIncomingMessageFromChild (2025-01-17T18:15:57.280Z): Sending message 8eb2d0b1-f2a4-4516-8afd-e9201699c9d9 (legacy id: 0) to child via postMessage, args = (2) ['authentication', 'web']) [c6f79d9e-8489-4510-9e34-970a4088c9d4] +0ms

Change file added:

Yes