ENH: Python dotenv

[kaitj]

Proposed changes

Makes use of the python-dotenv library to grab the configuration variables from a .env file without need to export the file prior to use. These changes were originally made based on an old version of master. This PR includes a rebase from the remaster-code branch, which is just waiting to be merged at the next meeting. Local tests have this working.

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionalitiy)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

• [x] Changes have been tested to ensure that fix is effective or that a feature works.
• [x] Changes pass the unit tests
• [x] Code has been run through black with the -l 79 flag.
• [x] I have included necessary documentation or comments (as necessary)
• [ ] Any dependent changes have been merged and published

Notes

All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

_PR template was adopted from appium_

[tkkuehn]

@kaitj Looks like some of the changes you made didn't get pushed to github?

[kaitj]

@kaitj Looks like some of the changes you made didn't get pushed to github?

Huh that was weird. It was staged but never committed.