[CBR-207] introduce 'katip'

[CodiePP]

Description

We want to switch libraries from ‘log-warper’ to ‘katip’ as the latter promises to easily support JSON logging which is needed for structured logging.

The external library ‘katip’ is registered as a dependency in ‘stack.yaml’ and the cabal file of module ‘util’, where the new logging’s implementation will reside. No current code must use the new library, except the new tests.

• no changes to existing code
• adding files to 'util' only

Linked issue

CBR-207
CBR-97 (user story)

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

[CodiePP]

tested this PR #3477 and PR #3476 rebased on develop again (reverted commit 06b4f09..) for block syncing. it worked up to epoch 16 where develop anyway fails.