[CLI] Pin fails when bumping to a newer version with a package that wasn't published on old version

[adrw]

Make pin resilient enough to not leave the tab in an unrecoverable state where

• the miskTab version hasn't been bumped
• AND package.json has been regenerated now to reference a new package with an old version (that was never published and doesn't exist)

Example

• @misk/prettier wasn't released until 0.1.15-ish
• Pin a tab from version 0.1.7 to latest (0.1.17)
• Pin fails and version remains at 0.1.7
• package.json gets regenerated but now to reference @misk/prettier @ 0.1.7 that doesn't exist
• Failure has to be manually resolved by setting the version in miskTab.json, running prebuild and then ci-build

Debug

[MIGRATE][ORDERS]
[GENERATE][ORDERS]
[WARN][ORDERS] Cannot resolve @misk/prettier@0.1.5 on NPM.
[GENERATE][ORDERS] Up to date build files generated using Misk Web @ 0.1.5

> misk-web-tab-orders@0.1.5 prebuild /Users/adrw/Development/cash-services/invest-broker-admin/service/web/tabs/orders
> npm run-script lint


> misk-web-tab-orders@0.1.5 lint /Users/adrw/Development/cash-services/invest-broker-admin/service/web/tabs/orders
> prettier --write --config package.json ".{/src/**/,/}*.{md,css,scss,less,json,js,jsx,ts,tsx}"

[error] Invalid configuration file: Cannot find module '@misk/prettier' from '/Users/adrw/Development/cash-services/invest-broker-admin/service/web/tabs/orders'