feat: add mutation type to validator and trigger execute functions

[wschurman]

Why

It's sometimes helpful to have information about what type of mutation is being executed when running validators/triggers, and in the case of update mutations what the previous value was. This is similar to the functionality expressible in rails with ActiveModel::Dirty.

Some examples:

• Only allow valid field state transitions on update mutations (finite state machine)
• Run only some logic on update in a validator

How

Add mutation info object to trigger and validator execution functions

Test Plan

Run tests.

[codecov]

Codecov Report

Merging #119 (cb09af6) into master (b11dbc0) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   95.08%   95.10%   +0.01%     
==========================================
  Files          67       67              
  Lines        1689     1694       +5     
  Branches      202      203       +1     
==========================================
+ Hits         1606     1611       +5     
  Misses         81       81              
  Partials        2        2              

Flag	Coverage Δ
integration	95.10% <100.00%> (+0.01%)	⬆️
unittest	95.10% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...s/entity/src/EntityMutationTriggerConfiguration.ts	100.00% <ø> (ø)
packages/entity/src/EntityMutatorFactory.ts	100.00% <ø> (ø)
packages/entity/src/EntityMutator.ts	98.20% <100.00%> (+0.05%)	⬆️

---

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 b11dbc0...cb09af6. Read the comment docs.