fix: set version in package-lock.json to match the current release

[jrgilman]

SUMMARY

The package-lock.json file currently refers to the previous 4.1.1 release, when the current release is 4.1.2. This is just a minor fix that corrects that.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Not applicable.

TESTING INSTRUCTIONS

If you run npm i currently it automatically makes this change. Thus all docker containers that get built already have this change. You can confirm this by building the containers, upping the containers, and then inspecting the file at /app/superset-frontend/package-lock.json.

ADDITIONAL INFORMATION

All are N/A below.

• [ ] Has associated issue:
• [ ] Required feature flags:
• [ ] Changes UI
• [ ] Includes DB Migration (follow approval process in SIP-59)
  • [ ] Migration is atomic, supports rollback & is backwards-compatible
  • [ ] Confirm DB migration upgrade and downgrade tested
  • [ ] Runtime estimates and downtime expectations provided
• [ ] Introduces new feature or API
• [ ] Removes existing feature or API

[michael-s-molina]

~~@jrgilman I'm not sure why package-lock.json is pointing to 4.1.1. It should reference the version in package.json.~~

[michael-s-molina]

@sadpandajoe Can you take a look? This is a commit to the 4.1 branch.