Add support for ENV of the form: ENV name=value ...

still supports the old form: ENV name value.
Notes:
- presence of "=" in the first word is the trigger to know if we're going the old vs new form
- new form supports quoting and \'s the same way the cmd line does

since shells support:
abc=123 def=456 <some-command>
I think supporting:
ENV abc=123 def=456
makes a lot of sense.  This isn't just about doing some kind of batching (which is being worked on in other PRs), this aligns ENV with what shells supports.

Keeping old description for posterity:
I have mixed feelings about this.  While it works and is kind of cool to be able to do:
ENV abc=def foo="feed the dog" hungry=eat\ a\ pizza late="go to bed 'now' I said"
and each key=value is parsed like you'd expect it to be on the command line, the ability to do more than
one ENV at a time really should be done under some kind of batching mechanism.  But, of course,
that's not there yet and we're not sure when it will be.  So, unlike the RUN command where we can
concat things together with &&'s, the ENV command doesn't have that option - not without this feature.

Closes #2333

Signed-off-by: Doug Davis <dug@us.ibm.com>