Refactor getting environment variables

[justinkaseman]

Maybe we could avoid some duplication with the other method? Like passing a boolean value e.g = (name: string, required = true, delimiter = ',', prefix = '') and use util.getRandomEnv('API_KEY') in all places.

Then we can call util.getRandomEnv('API_KEY', false) in places that we don't want the var to be required.

Or something similar.

Originally posted by @ebarakos in #226 (comment)

[ebarakos]

Tackling this in 08a5e4a (#293)(Dismissed this because it seemed like not providing much value)

[GMSteuart]

@justinkaseman any reason not to use dotenv

[boxhock]

@justinkaseman is this still relevant?

[alejoberardino]

I do think this would be a good change to make, there are many libraries that handle getting env vars and additionally defining a schema to validate them

[justinkaseman]

Closing in favor of EAv3