check for message-port-like methods should reach lower common denominator

[achou11]

Looking at this check:

rpc-reflector/lib/is-message-port-like.js

Lines 19 to 21 in 3cbcc1d

	typeof value.on === 'function' &&
	typeof value.off === 'function' &&
	typeof value.postMessage === 'function'

I think this should be doing addEventListener and removeEventListener to align with the EventTarget interface, which MessagePort should extend. I think on and off are more strictly related to Node's implementation and are usually just aliases of add/remove event listener.

Example of additional work needed when integrating rpc-reflector is somewhat describe here, where the channel in question didn't have on and off methods and so a custom class had to be created to emulate the checked interface (digidem/comapeo-mobile#8):

separate implementations of MessagePortLike. this is because the nodejs-mobile channel extends different behaving classes based on the environment (Node's EventEmitter in the nodejs-mobile process but React Native's EventEmitter in the React Native runtime). Due to the different APIs and behaviors between the two, creating a shared implementation is not trivial and more overhead than necessary.

[achou11]

turns out node's event emitter doesn't implement addEventListener and removeEventListener 🤦‍♂️ Still, maybe at least check for addListener and removeListener