Add Blueprint.prototype.lookupBlueprint.

Allows custom blueprints to inherit the `files` from another
blueprint without requiring `ember-cli` itself
run ember with node

shebangs don't work on windows so the script is not executable
Merge pull request #2016 from rwjblue/allow-blueprint-to-access-other-blueprints

Add Blueprint.prototype.lookupBlueprint.
[windows] - force AMD paths on windows in Addon.includedModules
Update Blueprint’s inline docs
Merge pull request #2022 from jgwhite/update-blueprint-inline-docs

Update Blueprint’s inline docs
Merge pull request #2021 from raytiley/win-addon-includedmodules

[windows] - normalize filePath when calculating Addon.includedModules
Merge pull request #1682 from raytiley/win-run-command

run ember with node (windows test fixes)
Update CHANGELOG.
Pull `podModulePrefix` from config/environment.js.

This brings using a custom pod prefix inline with the normal
`modulePrefix`.  If not defined (by default it isn't) then it will just
fallback to `modulePrefix` (this done
[here](https://github.com/stefanpenner/ember-jj-abrams-resolver/blob/master/packages/ember-resolver/lib/core.js#L171)).
[windows] - make configPath test work on windows
[windows] split output on unix line endings

Looks like inquirer which is used by ui for creating prompts uses unix
line endings instead of enviornment specific. This causes the tests that
split the output to run assertions to fail.

Switched those specific tests to split on unix line endings as that split
the lines at the same place anyway and none of the regex are specific
enough to care about the extra `\r`
Merge pull request #2019 from raytiley/win-project-tests

[windows] - make configPath test work on windows
Merge pull request #2017 from raytiley/win-blueprint-test

[windows] split output on unix line endings for blueprint tests
Merge pull request #2024 from rwjblue/use-pod-module-prefix

Pull `podModulePrefix` from config/environment.js.
[windows] filterpattern test works on windows

This is the simplest fix to make the test pass. It raises the question of
wether the LiveReloadServer should normalize the slashes in the
filterPatterns so the same pattern can work on different OS. If not the
user would have to craft regex which aren't OS specific, or provided to
filters.