feat(ng new): Make CLI available without install

[Meligy]

This small change will allow consumers of the CLI to have their projects shared with anyone, even if they don't have the CLI installed.

They just clone, and run npm install, and then they can all interesting stuff they want directly from the CLI by using npm run ng -- instead of ng.

It also helps people who may have multiple projects created by the CLI not all upgraded to the latest version, matching their global install.

[filipesilva]

This might work for some commands but it's not guaranteed to work for every one.

@hansl @Brocco what do you think?

[Meligy]

I use it this way in several projects on Mac and Windows and been doing so for months (it's the first change I make after ng new).

Note that this is how npm start and npm test work today.

[Meligy]

@hansl @Brocco would you guys think this is an OK default?
(It seems to be getting a few +1`s)

The PR doesn't try to push using it as front and center best practice or anything. It's just a nice reliable option when people have the CLI version it lands in, and other more recent versions.

[hansl]

I'm okay with this, although this will break in the future when we actually remove the CLI from dependencies of projects.

@filipesilva @Brocco do either of you have a problem with this change?

[filipesilva]

I am ok with it.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}