dev-deploy: create neardev directory if it doesn't exist

[mikedotexe]

If there's no neardev directory, near dev-deploy will fail with:

Error:  [Error: ENOENT: no such file or directory, open 'neardev/dev-account'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'neardev/dev-account'
}
error Command failed with exit code 1.

This is new behavior as of 0.23.0, let's address this quickly.

Tested by going into guest-book example locally:
../near-shell/bin/near dev-deploy

rm -rf neardev
then running it again
rm neardev/dev-account*
then running it again

[chadoh]

I would prefer we did the equivalent of mkdir -p in the normal flow, rather than creating the directory in the catch block

[mikedotexe]

I would prefer we did the equivalent of mkdir -p in the normal flow, rather than creating the directory in the catch block

That won't work for Windows, but I did consider adding the mkdir package for this. I know there's always pushback against adding new dependencies for one small change, so I decided to do it this way.

[chadoh]

Right, I said "something like mkdir -p because I thought windows might give problems with actual mkdir -p.

I think we could use something like this:

if (!fs.existsSync('./neardev')) await fs.promises.mkdir('./neardev')

(Not sure I got that syntax right)

Would this work on Windows?

[vgrichina]

This change d426201 only works well if all the occurrences are replaced:
https://github.com/near/near-shell/search?l=JavaScript&q=neardev