[5.0] Allow For Per-Deploy Environment Config Overrides

This is my suggestion to solve #5951.

For local / per-developer / per-installation / per-deploy configs, this allows for adding e.g. a config/developers/mail.local.php. This would not be added to version control. The file would probably contain some mailer API credentials for the current developer. It would only be loaded on his machine if Laravel runs in the "developers" environment.

This is super-simple and it would be a nice built-in workflow for the problems described in #5951.

Thoughts?

---

I realize tests are probably failing, this is just meant to start a discussion. I will fix the tests (and add new ones) and clean up the code a bit once this gets some support.

This will also be accompanied by another PR to laravel/laravel that would add `*.local.php` to a `.gitignore` file in the config directory.
`elseif` as one word please.