Handle Blazegraph corruption of special characters

[NZT48]

Description

This PR handles situation when Blazegraph corrupts data on reading. This is affecting special characters like emojis, which are returned in format of \U0001f600 instead of 😀. Additionally, try-catch is added to avoid infinite loop of state finalized processing, which happens with unexpected errors like the one mentioned before.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Manual testing using DKG.js client
• BDD tests

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes