Properly sort added dependency during init

[evocateur]

Unfortunately, there are no tests for the InitCommand. In any case, here's a demonstration of what this patch fixes:

Before

$ cat package.json
{
  "name": "test",
  "devDependencies" {
    "eslint": "^3.9.1"
  }
}
$ asini init --loglevel=silent
$ cat package.json
{
  "name": "test",
  "devDependencies" {
    "eslint": "^3.9.1",
    "asini": "1.2.0"
  }
}

After

$ cat package.json
{
  "name": "test",
  "devDependencies" {
    "eslint": "^3.9.1"
  }
}
$ asini init --loglevel=silent
$ cat package.json
{
  "name": "test",
  "devDependencies" {
    "asini": "1.2.0",
    "eslint": "^3.9.1"
  }
}

It seems to do fine with sorting when asini already exists, but fails to properly replace the referenced object when asini is being added to the dependencies.

I also removed the irrelevant lerna stuff.

[gigabo]

Oh, man... what is this I don't even... :squint:

I must have botched a port of a Lerna patch somehow.

Thanks for cleaning this up while you were in here @evocateur!

[gigabo]

This is great. It more closely matches what npm itself does when adding dependencies.

Thanks @evocateur!