Update Communicator to include app metadata

[cb-jake]

Summary

This change initializes the communicator with the app metadata. This provides app metadata to the onboarding screen on keys.coinbase.com

How did you test your changes?

Testing these changes requires running a few apps:

• Playground
• SCW.

1. build a version of the sdk and install it into the playground. Make sure the playground is using the newly built version
2. run the playground and scw locally (place a log where the communicator is initialized)
3. Check the message event from the sdks communicator and validate appName, and appLogoUrl are available inside of scw.

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 1/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[bangtoven]

i wonder whether this needs to be a param of waitForPopupLoaded method, not in constructor level.
(btw, we might rename the method to be, initialize or connect maybe??)
@cb-jake

[cb-jake]

@bangtoven If we made it a param of waitForPopupLoaded we would probably need to make it a param postMessage as well which would require passing it on calls to postMessage. Currently we call waitForPopupLoaded in 2 places, though one of those places is inside the communicators postmessage method which is called in 4 spots. I'm not positive we would have access to the metadata in all spots we call these methods

[bangtoven]

we should revisit Communicator's implementation so that we can understand when it should pass metadata to popup. probably only for onboarding or handshake, not all messages.