[CBR-430] add version and configuration key to JSON logs

[CodiePP]

Description

add cardano-sl version and configuration key to the "env" field in JSON logs.

Linked issue

CBR-430

Type of change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🛠 New feature (non-breaking change which adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
• 🔨 New or improved tests for existing code
• ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

• I have read the style guide document, and my code follows the code style of this project.
• [~] If my code deals with exceptions, it follows the guidelines.
• [~] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
• [~] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

• [~] I have added tests to cover my changes.
• All new and existing tests passed.

QA Steps

Screenshots (if available)

{
  "at": "2018-09-13T22:57:32.067585Z",
  "env": "mainnet_wallet_macos64:1.3.0",
  "ns": [
    "cardano-sl",
    "*production*"
  ],
  "data": {},
  "app": [
    "cardano-sl"
  ],
  "msg": "Verifying and applying blocks...",
  "pid": "25767",
  "loc": null,
  "host": "hostname",
  "sev": "Info",
  "thread": "ThreadId 1996"
}

[ksaric]

LGTM.

[ksaric]

configurationKey? Then again, it's used all over the place with this convention 🤷‍♂️

[CodiePP]

now with setupTestLogging and setupTestTrace
rebased on develop