chore: fix package-lock and add git diff check

[bchew]

Description

• fix package-lock
• switch to use npm install instead of npm ci so that we can validate changes
• add git diff check to fail CI to catch incorrect package-lock changes

Motivation and Background Context

Although npm ci is faster, changing travis-ci to use npm install instead so that we can catch incorrectly pushed package-lock changes.

Does this PR introduce a breaking change?

• Yes
• No

How Has This Been Tested?

Screenshots (if appropriate):

Check-list:

• I have read the Contributing document.
• I've thought about and labelled my PR/commit message appropriately.
• If this PR introduces breaking changes I've described the impact and migration path for existing applications.
• CI is green (coverage, linting, tests).
• I have updated the documentation accordingly.
• I've two LGTMs/Approvals.
• I've fixed or replied to all my code-review comments.
• I've manually tested with a buddy.
• I've squashed my commits into one.

[xiaofan2406]

LGTM

[codecov-io]

Codecov Report

Merging #842 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #842   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          69     69           
  Lines        1007   1007           
  Branches      230    230           
=====================================
  Hits         1007   1007

---

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 57f41ae...723bf7e. Read the comment docs.

[lightbringer1991]

LGTM

[lightbringer1991]

merging...