fix(gatsby-dev-cli): fix "expected manifest" errors

[pieh]

I was checking on one instance of "expected manifest" error and seems like in some cases using dist-tag over concrete version when installing dependencies was triggering this problem (problem in yarn perhaps?). Using concrete versions seems to solve it (at least in reproduction I had).

There are also few QoL improvements:

• increase request retries for npm registry uplink - on flaky connections (or maybe when npm registry is getting hammered) installation would sometimes fail because of those - this adds bit more resilience
• don't display those annoying and not actionable "Installation of dependencies after initial scan is not implemented" messages when package.json is being changed by gatsby-dev itself while publishing dev versions of packages
• in case of yarn installation failures - exit the process and don't continue - this particulary annoying because of output spam when you don't use --quiet you don't actually see that installation failed, and gatsby-dev continued to copy files phase resulting in not installed packages, just copied files in node_modules

You try it by installing qol canary: npm i -g gatsby-dev-cli@qol