Some improvements

[iliaamiri]

Fixed

• Fixed mightFail.all type inference by using the type signature for Promise.all in the ES2015 Promise Constructor instead of Iterator because the former gives tuple level type hinting vs. the latter doesn't.
• Fix part of the mightFail.any's error type is inaccurate #20 issue with having to cast the error to AggregateError

Changed

• Removed mightFail.allSettled as it is unnecessary because Promise.allSettled never throws an error.
• Change the prettier new line to LF because it's what Unix-based systems use vs. CLRF is what Windows uses. And we hate Windows of course.
• Format some lines based on the prettier config

[meech-ward]

does E extends Error = Error mean that it defaults to Error but can be any custom subclass/subtype of error?

why does it not work already with the way Either works?

[iliaamiri]

Yep exactly. The issue was that the exact subtype of Error doesn't infer at all. For example in the Promise.all method, when error happens, the error should be AggregateError but I had to manually cast it myself.

Or just generally when a dev wants to throw a custom Error, they can't see the real type cause the type doesn't infer because we gave a concrete Error type to the Either instead of a generic one.