Dependencies with * as version range fetches version non-existing 0.0.0

Given a dependency such as:

```json
{
"peerDependencies": {
"awesome-lib": "*"
}
}
```

This yields the error:

> Warning: 3:5 warning "awesome-lib@0.0.0" is not published to the NPM registry no-deprecated-dependency

In this case we should fetch the lowest published version to check against.

Start by tracing the no-deprecated-dependency check for peerDependencies and the code that resolves "*" against the NPM registry. Reproduce the issue with the package.json example, then verify that the lowest published version is used instead of 0.0.0 and that the warning no longer reports a nonexistent version.

Written by the indexing model from the issue text.