ENYO-3012: fix interaction between `-s` & `-p` + use `packagejs:` in `deploy.json`

- the `source:` property of `deploy.json` did not make sense as it was
  always refering  to the  folder where `deploy.json`  is.  it  is now
  replaced by a `packagejs:`  property (default: `"package.js"`) which
  indicates  where   is  the   relative  location  of   the  top-level
  `package.js` from the project root folder.
- only interaction left between `-s|--source` and `-p|--packagejs` is:
  
  > if `--source` is not provided and `--packagejs` is provided, then
  > `--source` is assumed to be the folder containing the given
  > `--packagejs`

- precedence order for `package.js` location is now
  1. from command-line
  2. from `deploy.json` 
  3. default value `"./package.js"`

Enyo-DCO-1.1-Signed-off-by: Francois-Xavier KOWALSKI <francois-xavier.kowalski@hp.com>
ENYO-3012: (less) fix case where `package.js` deep (>1) in the source tree

less-generated assets need to  be referred to from `build/index.html`,
not from the folder where the top-level `package.js` is living.

Enyo-DCO-1.1-Signed-off-by: Francois-Xavier KOWALSKI <francois-xavier.kowalski@hp.com>
ENYO-3012: be more explicit about folders creation during verbose execution

Enyo-DCO-1.1-Signed-off-by: Francois-Xavier KOWALSKI <francois-xavier.kowalski@hp.com>
ENYO-3012: jshint/ tabs+spaces => spaces

Enyo-DCO-1.1-Signed-off-by: Francois-Xavier KOWALSKI <francois-xavier.kowalski@hp.com>
GF-35208: fix dispatch system so delgated events are only dispatched to the immediate owners

* make meaning of "delegate" property on event the destination object, not the source
* Remove unused code from the old delegation system.
* Include test case from this bug report in ComponentDispatchTest.js

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
Restore previous interpretation of delegate property -- needed to have correct sender.

* Added test for redispatch to detect this error.

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
Update version to 2.3.0-pre.9-dev\n\nEnyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
Merge pull request #434 from enyojs/ENYO-3012

ENYO-3012: bad asset path after deploying a non-Bootplate-like Enyo application

Reviewed-By: Ben Combee (ben.combee@lge.com)
Fixed Async.failed state being retained between calls to Ajax.go()'
Merge pull request #441 from vtomilin/master

Fixed Async.failed state being retained between calls to Ajax.go()'

Reviewed-By: Ben Combee (ben.combee@lge.com)
Don't create __jobs hash in enyo.Component until it's used to reduce startup time

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
Merge pull request #442 from enyojs/reduce-jobs-overhead

Don't create __jobs hash in enyo.Component until it's used to reduce sta...

Reviewed-By: Cole Davis (cole.davis@lge.com)
API summary cleanup. Enyo-DCO-1.1-Signed-Off-By: Jim Tang (jim.tang@lge.com)
ENYO-3080: Fix duplicate key in package.json

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
API comment cleanup. Enyo-DCO-1.1-Signed-Off-By: Jim Tang (jim.tang@lge.com)
API comment cleanup. Enyo-DCO-1.1-Signed-Off-By: Jim Tang (jim.tang@lge.com)
Use a queue for all enyo.ready() calls, not just ones before DOMContentReady.

This is to speed up app launch into a container when source is loaded after the initial app startup.

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)
Merge pull request #443 from enyojs/combine-enyo-ready-calls

Use a queue for all enyo.ready() calls, not just ones before DOMContentR...

Reviewed-By: Cole Davis (cole.davis@lge.com)
Facade interval (Animation time step) from ScrollMath to TouchScrollStrategy.

Enyo-DCO-1.1-Signed-off-by: Kunmyon Choi <kunmyon.choi@lge.com>
Avoid cloning observer maps for instances until needed for local modifications.

Enyo-DCO-1.1-Signed-Off-By: Ben Combee (ben.combee@lge.com)