Flip the argument order of Future.or

[Avaq]

I though and had the wrong order of arguments, but really it was or all-along. I think both and and or should have non-inverted arguments (as opposed to most static functions), so:

Future.ap(a, b)  === b.ap(a);
Future.or(a, b)  === a.or(b);
Future.and(a, b) === a.and(b);

I think this is much more expected behavior, and has the arguments in the right order for reduce.

[codecov-io]

Codecov Report

Merging #74 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #74   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines         929    929           
  Branches      219    219           
=====================================
  Hits          929    929

Impacted Files	Coverage Δ
fluture.js	100% <100%> (ø)	✅

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6af85fd...c23956c. Read the comment docs.