Nissix plugin scope-packages on ambassador-conflict

[deanshub]

Hi, I'm Nissix, the automated PR bot!

Wix is moving its internal packages to the @wix scope (but still in the internal registry). Publishing new unscoped internal packages is no longer allowed, and all existing packages are moving to @wix. This means changing package names, and also all usages of those packages to their @wix scope version.

This PR is an automatic codemod that moves all of your packages to @wix scope, and changes any usages (pacakge.json, imports, requires, etc..) to their @wix version.

‼️	This codemod is best-effort! Meaning it may not have found and fixed all usages, but it did change your package.jsons. So go over the changes carefully and test this version carefully

If you want to know why we don't support publishing unscoped to the internal registry, check out this article on Dependency Confusion

If you are unsure, need help or have questions, reach us at #wix-scope-migration

Error Log:
npx: installed 234 in 6.135s

Output Log:
Migrating package "ambassador-conflict" in serverless/ambassador-conflict

Migration from non scope to @wix/scoped packages

/tmp/4c59206921a6e6edcae5623c06b1e660/serverless/ambassador-conflict

rename package.json dependencies/dev/bundled/peer/optional, jest & eslintConfig

package.json

replace import/require in js/ts files

serverless.js