feat(neon): Implement TryIntoJs/TryFromJs for either::Either

[kjvalencik]

This implements the extract traits for either::Either. I chose not to feature flag it because either is a very small crate with zero dependencies.

The Ok implementation paths were very clear. However, there isn't an obviously correct implementation for a failed TryFromJs.

We have two errors, both L::Error and R::Error. This PR does the following:

• Creates a new Error that prints the type name of L and R saying that they failed
• Attaches left and right keys to the error object with their TryIntoJs implementation

Another option would be to return only one of the errors. Unfortunately, we can't attach one error to the other because it might not be an Object.

What's the best thing to do for this?

[dherman]

What's the best thing to do for this?

I agree with what you did. Two errors occurred, so neither should be dropped; the caller needs to decide what to do and should have full access to both. It kind of reminds me of how exception cause chaining preserves a history for introspection.

[dherman]

Short and sweet!

🚢