Feature - Handling Environments

This PR was created for the purpose of handling different environments and building them into classes that can be strictly type checked.

The EnvironmentFactory class can either take in a string, use the current `ENVIRONMENT` variable, or default to a `development` environment.

If the environment isn't recognized as one of the defined (development, staging, production) we create a CustomEnvironment class which will allow for custom configurations in the future.
Yea, if there were more classes other than just the factory, I'd agree. But that's not the case. Also, it makes it so that the factory has to include each and every class its building, which wouldn't be necessary if they shared a namespace.