Update package-lock.json after a fresh `npm install`
Update package-lock.json after a fresh `npm install`

…so that I have a known baseline for subsequent dep upgrades driven by
security vulnerabilities.

I believe changes (except for own our version bump) are due to new
upstream versions compatible with our declared semver ranges.  This is
the seemingly-stable file content after running `npm install` three
times starting from no node_modules/.  It produced this content after
the second run and it remained unchanged after the third.

nextstrain/auspice,nextstrain/auspice,nextstrain/auspice