fix(serve): Removes logic looking for config/environment.js in the project root

[celliott181]

This removes the logic for ember-cli config files in the project root. Previously the CLI package would break when this file was present and ng serve was performed. It would remain unusable until the config/environment.js file is removed and npm install is performed again.

This allows the project to be served with the config/environment.js file in place. Fixes #3531

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

[celliott181]

I signed it (rebased to the proper account actually)!

[googlebot]

CLAs look good, thanks!

[hansl]

LGTM, thanks. Could you rebase?

[filipesilva]

@gelliott181 sorry it took so long to get this reviewed and merged. Can you rebase though? We changed the structure and this file is now somewhere else.

[celliott181]

Did you get the rebased commit? I did it late one night and wasn't sure if I pushed my master.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}