Issue title: E2E Protractor: returned promises do not get resolved
 Issue body: <!--
BUGS: Please use this template.

SUPPORT REQUESTS/QUESTIONS: If you have a support request or question please
submit them to StackOverflow using the tag `[aurelia]`
http://stackoverflow.com/questions/tagged/aurelia
or the Aurelia Gitter https://gitter.im/aurelia/discuss

Blue Spire offers paid support agreements. Further information regarding paid support
may be obtained by emailing crystal39@example.net

Future support requests submitted here will be closed.

The HTML comments below are for your reference, and are not displayed
when your issue is submitted, feel free to leave them.

Choose one of the two headings, delete the other.
-->
**I'm submitting a bug report**

* **Aurelia Skeleton Version**
skeleton-esnext
skeleton-typescript

<!-- Delete any skeleton versions this DOES NOT apply to -->

* **Framework Version:**
1.0.6

**Please tell us about your environment:**
* **Operating System:**
Windows 10

* **Node Version:**
8.1.3
<!--
Minimum supported Node version is latest Node 4.x LTS
run `node -v`
-->

* **NPM Version:**
5.0.3
<!--
MINIMUM SUPPOERTED NPM VERSION IS 3.x. NPM 2.x WILL NOT WORK.
run `npm -v`
-->

* **JSPM OR Webpack AND Version**
JSPM 0.16.53
<!--
If using JSPM
run `jspm -v`
If using Webpack
run `webpack --help | grep webpack`
-->

* **Browser:**
hrome  59.0.3071.115  

* **Language:**
all | TypeScript X.X | ESNext


**Current behavior:**
Returned promises do not get resolved.
For example, in file skeleton.po.ts 
 getCurrentPageTitle() {
    let title = browser.getTitle();
    console.log(title); //Promise is logged
    title.then((resp)=>{console.log(resp);}) //Page title (Aurelia) is logged
    return title;
  }

After downloading skeleton and doing:
1.  npm install
2. jspm install
3. gulp webdriver-update 
and then gulp watch and gulp e2e, all tests fail because everything is compared to promise object.


**Expected/desired behavior:**
Promises should be resolved.
<!--
If the current behavior is a bug, please provide the steps to reproduce and, if possible, a minimal demo of the
problem along with a runnable gist, if possible.
To create a runnable gist, go to https://gist.run/?id=7542e061bc940cde506b&sha=6821c521a6c7bae6f59a36fb8628ecd1032b2d10
Then click "Fork to Public Gist".
Create your gist, then finally click "Update Gist." Include a link to the gist.run below.
-->

 Comments: 
 Comment 0: Please see the way this is solved in Webpack skeletons. We'll be deprecating the JSPM skeletons soon, since it was a nightmare to maintain them all (#845) (not support for JSPM though, we're keeping that!).
 Comment 1: So would you generally recommend switching to webpack setup?
 Comment 2: @zeko77 it's really up to you (as I said, we're keeping support for JSPM, just not in the skeletons), but many Aurelia users (including me) have found Webpack to be a better overall setup.
 Comment 3: @zeko77 I'd recommend that you either use a pure Webpack setup or use the Aurelia CLI.
{'source': 'GithubIssues', 'repo_name_with_owner': 'aurelia/skeleton-navigation', 'issue_id': 239749731, 'repo_stars': 878.0}