Update/gutenberg jetpack and package lock

[mkevins]

Update Jetpack and Gutenberg reference, and update package lockfile.

To test:
Tests should pass on CI.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[hypest]

👋 Matthew! Took the liberty to push the package-lock.json that my local npm install produces (node v14.17.0, npm v6.14.13 that get installed via nvm install inside the gutenberg subfolder). Let's see it that will fix the mismatch.

[hypest]

The Correctness CI job fails with some eslint issues, most probably related to outdated way we invoke it. I left a comment on a relevant PR for help but, take a look too @mkevins if you can get to it, thanks!

[mkevins]

Matthew! Took the liberty to push the package-lock.json that my local npm install produces (node v14.17.0, npm v6.14.13 that get installed via nvm install inside the gutenberg subfolder). Let's see it that will fix the mismatch.

Thanks Stefanos! Following up on the repllies in the thread of the relevant PR, I updated the version of eslint-pluging-jsdoc in gutenberg-mobile to align with the version used in gutenberg, and that seemingly resolved the issues we were seeing on CI.

I did not track down where / why we have our own dependency on the eslint-plugin-jsdoc, or whether it makes sense to remove it. For now, I focused on getting CI green for other PRs (especially the release PRs).

Also, for some reason when I ran npm run lint locally (which then runs eslint . --ext .js) it seemed to hang indefinitely, with CPU ~ 100%. 🤷‍♂️

[antonis]

Thank you @mkevins and @hypest for handling this 🙇

I updated the version of eslint-pluging-jsdoc in gutenberg-mobile to align with the version used in gutenberg, and that seemingly resolved the issues we were seeing on CI.

The change LGTM and seems to work fine since the CI is green 🎉

I did not track down where / why we have our own dependency on the eslint-plugin-jsdoc, or whether it makes sense to remove it.

That's a good point. Maybe we should revisit this 🤔

[mkevins]

Thanks for reviewing Antonis!