[#49] Escaping characters in parse errors

[DK318]

Description

Problem

We are not escaping failing input in parse errors. Some characters can be invisible (e.g. zero width space) so user can't figure out what is going on when he sees parse error.

Solution

Escaping failing input in parse errors.

Related issue(s)

• Fixes #49

  Related changes (conditional)

  • Tests

    • [x] If I added new functionality, I added tests covering it.
    • [x] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

  • Documentation

    • [x] I checked whether I should update the docs and did so if necessary:
    • README
    • Haddock

  • Public contracts

    • [x] Any modifications of public contracts comply with the Evolution of Public Contracts policy.
    • [x] I added an entry to the changelog if my changes are visible to the users and
    • [x] provided a migration guide for breaking changes if possible

  Stylistic guide (mandatory)

  • [x] My commits comply with the policy used in Serokell.
  • [x] My code complies with the style guide.