#160045670 use dot env files to load Environmental variables

[krmroland]

What does this PR do?

Currently, all configuration values are placed in a single config file including those that should be kept secret e.g the Database Variables

This PR gives an opportunity to put the secret variables in a private .env whose values can be exported to environmental variables using python-dotenv.

How should this be manually tested?

Since the variables located in the .env are secret variables, .env is blacklisted from VCS, however an example of how the .env file looks like is given, just rename .env.example to .env and replace the dummy values with actual values

• Refer to README.md for setup instructions

What are the relevant pivotal tracker stories?

#160045670

[coveralls]

Pull Request Test Coverage Report for Build 82

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 77:	0.0%
Covered Lines:	163
Relevant Lines:	163

---

💛 - Coveralls

[krmroland]

@RachaelNantale, How about this??