Align NodeTask interface to bettter match up with Exec / JavaExec

[dougborg]

Right now the NodeTask task interface is a bit different than the interface on the standard Exec task. While I understand the implementation details behind these differences, I think it would be possible to have the NodeTask interface better match up with the standard Exec interface.

The main sticking points I have noticed so far:

1. You have to use the execOverrides closure to set environment and other exec details rather than just having those attached to the main task definition / configuration closure.
2. You have to assign args via the property args = ['an', 'array', 'of', 'arguments'] instead of a method args 'a', 'list', 'of', 'method', 'arguments'

There may be others - let me know what you think.

[srs]

Sorry about the long delay. I had too much to do in my daytime job in the last couple of months. Yes, I think this is a good idea. Aligning with Exec interface makes sense.

[Globegitter]

@srs Maybe that is not directly related, but there is another issue I am running into. When I run gradle yarn_run_start which starts up a dev-server, if I then try to CTRL+C out of it the server stays running and the port open in the background. So I have to manually kill the process. Is there any other workaround to that?