* chore: switch to leven

* chore: update lock file

* chore: iterate through all the available commands and find closest match

* chore: update yarn.lock

* fix: lint

* chore: find the best possible match

* Added basic upgrading instructions

* Update docs/guide/installation.md

Co-Authored-By: Natalia Tepluhina <tarya.se@gmail.com>

* Update docs/guide/installation.md

Co-Authored-By: Natalia Tepluhina <tarya.se@gmail.com>

Co-authored-by: Natalia Tepluhina <tarya.se@gmail.com>

* chore: typographical fix

* chore: update test

ref to en docs

closes #5194

…#5202)

Currently, if we use `api.extendPackage({foo: null}, {prune: true})` the dependency is removed but a warning is logged as the range is invalid:

```
 WARN  invalid version range for dependency "foo":

- null injected by generator "my-plugin"
```

… packages (#5163)

closes #5161

The root cause of such issues:

`vue-jscodeshift-adapter` requires `vue-template-compiler`.
`vue-template-compiler` tries to require the `vue` package and check
its version on startup.

Normally, there's no `vue` package in the dependency tree of `@vue/cli`,
so this check will just skip.

But if the user has installed some other global package that depend on
`vue`, and hoists it to the root `node_modules`, `vue-template-compiler`
would successfully require it and check against that `vue` version,
which sometimes may be outdated, thus failing the bootstrap process.