Inspect mode

[homer0]

What does this PR do?

It finally brings the option to use the Node inspector for Node targets.

The feature description is on the documents, so you can get it from there; instead, I'll try to describe the code changes:

• Node targets now have an inspect settings group to configure the inspector and enable it for when the target runs on development.
• The node runner was updated to support both the native inspector and the new Google's ndb.
• The build command now can receive an --inspect flag.
• There's a new inspect command, which is a shortcut of build --run --inspect.
• nodemon is not longer executed with a settings object but with a string, to add support for the native inspector inspect flag.
• While reading the nodemon documentation, I saw the --legacy-watch, so I implemented it as a project configuration on the others category.

And this is breaking because...

• BuildNodeRunner now requires projectConfiguration (to get the legacy watch setting).
• buildNodeRunnerProcess is not longer BuildNodeRunnerProcess#run, but the class instance itself, because BuildNodeRunner needed access to the enableLegacyWatch method.
• BuildNodeRunnerProcess#run now requires a new parameter with the inspect options.

How should it be tested manually?

Since the webpack and Rollup plugins haven't been updated (yet), you can only test this with targets that don't require bundling:

yarn projext inspect [target]

and of course...

npm test
# or
yarn test

[coveralls]

Pull Request Test Coverage Report for Build 199

• 85 of 85 (100.0%) changed or added relevant lines in 14 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 196:	0.0%
Covered Lines:	1908
Relevant Lines:	1908

---

💛 - Coveralls