Add ability to ignore validation on Parse.Object constructor/set()

[TylerBrock]

This is an attempt to resolve the first blocker in #73.

Not sure if the Flow typing is correct but I'm sure you'll let me know if it is not.

[codecov-io]

Current coverage is 85.30%

Merging #74 into master will decrease coverage by -0.02% as of a51c23b

@@            master    #74   diff @@
=====================================
  Files           37     37       
  Stmts         2793   2796     +3
  Branches         0      0       
  Methods          0      0       
=====================================
+ Hit           2383   2385     +2
  Partial          0      0       
- Missed         410    411     +1

Review entire Coverage Diff as of a51c23b

Powered by Codecov. Updated on successful CI builds.

[TylerBrock]

The coverage tool doesn't seem to understand the constructor arguments being split into multiple lines. Cest la vies, eh?

[andrewimm]

Thought: it might make more sense to wrap this entire var validation = ...; if (...) {} block in an
if (!options.ignoreValidation) statement. That way, we don't needlessly run the validation logic.

[TylerBrock]

Yeah, for sure. I'll update the request.

[TylerBrock]

I'm also not thrilled with the API. I think a {deferValidation: true} on the constructor that just defers validation for all sets until persistence time might be better. Would love to hear your thoughts.

[TylerBrock]

Bump, lets get this rocking and rolling. I'd like to update our codebase without fear that this isn't going into the SDK. If there are issues or concerns lets discuss.

[andrewimm]

I like it. I think every entry point is covered (there are a lot of constructors due to supporting the old .extends()). Tests seem good to me.