Bump got and npx in /dev-environment/shared-projects-workspace

[dependabot]

Removes got. It's no longer used after updating ancestor dependency npx. These dependencies need to be updated together.

Removes got

Updates npx from 3.0.0 to 10.2.2

Changelog

Sourced from npx's changelog.

10.2.2 (2020-01-28)

Bug Fixes

• correct Kat's github url (9a23db1)
• install latest npm on travis for node 6 (e0eb3cb)
• Update changelog to fix old issue links (3733137)

10.2.0 (2018-04-13)

Bug Fixes

• i18n: fix korean; 쉘 -> 셸 (#163) (11d9fe0)
• spawn: spawn child processes with node without relying on the shebang. (#174) (cba97bb)
• windows: Allow spaces in the node path when using --node-arg (#173) (fe0d48a), closes #170

Features

• i18n: add translation (#159) (5da008b)

10.1.1 (2018-04-12)

10.1.0 (2018-04-12)

Features

• spawn: add --always-spawn to opt out of process takeover optimization feature (#172) (c0d6abc)

10.0.1 (2018-03-08)

Bug Fixes

• i18n: Improve French localization (#158) (c88823e)

... (truncated)

Commits

• 26a8394 chore(release): 10.2.2
• e0eb3cb fix: install latest npm on travis for node 6
• e8b4a7e chore: put node 6 back in travis set
• 9a23db1 fix: correct Kat's github url
• 3733137 fix: Update changelog to fix old issue links
• 3192e0f v10.2.1
• 40df81c fix: point repo at proper git remote
• 43d68c8 fix: spurious test failure
• f51a8d3 travis: only test on supported node versions
• b7c8b9f fix(platform): drop node 4 and 7, add 9 and 10
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​npx@​3.0.0 ⏵ 10.2.2	-18		+1	+1	-30

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		npm/npx@10.2.2 has Obfuscated code. Confidence: 0.92 Location: Package overview From: dev-environment/shared-projects-workspace/package-lock.json → npm/npx@10.2.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npx@10.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		npm/npx@10.2.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: dev-environment/shared-projects-workspace/package-lock.json → npm/npx@10.2.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npx@10.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report