feat: support advanced zap configuration

[maxime1907]

*Issue number of the reported bug or feature request: #123 *

Describe your changes

1. Removed the nasty DEBUG environment variable that is loaded outside of swagger's parser.
2. Added a command line argument --zap-config that points to a valid json zap config file
3. Added a /config folder to store the zap config file
4. Added a default zap config file under config/zap.json

Testing performed
Loaded different zap configuration files such as zap.prod.json, zap.dev.json to test that the log level and outputPaths are the correct ones.

[maxime1907]

cc @seeker89

[seeker89]

Hey @maxime1907 thanks for the PR!

Why was the DEBUG gate "nasty"?

I like adding the support for zap config file, but I'd prefer goldpinger to start (say with dev defaults) if none is provided - from the quick look I had it looks like it will now fail if there is none?

[maxime1907]

Hey @maxime1907 thanks for the PR!

Why was the DEBUG gate "nasty"?

I like adding the support for zap config file, but I'd prefer goldpinger to start (say with dev defaults) if none is provided - from the quick look I had it looks like it will now fail if there is none?

Hey!
I used the word nasty because i saw this comment in the code:

// We haven't parsed flags at this stage and that might be error prone

Yes it will be failing if no option is provided but i can make it work so that it loads default dev values no problem!

[maxime1907]

done! 🙂 @seeker89

[maxime1907]

Any updates @seeker89 ? ^^

[seeker89]

This will go out as v3.7.0

[seeker89]

Hey @maxime1907 sorry for the delay. Looks good. Please bump the version to 3.7.0 and let's get that money!

[maxime1907]

Hey @maxime1907 sorry for the delay. Looks good. Please bump the version to 3.7.0 and let's get that money!

Done @seeker89 !