There were several issues with Unicode support in MuranoPL
after switch to yaql 1.0. Each of those issues caused any deploy
to fail if it used to do anything with non-ASCII strings
Fixed issues are:
* Unicode strings should not be encoded to str types anymore.
yaql 1.0 has native support for the Unicode and fails when non-
ASCII chars encounter in str expressions. Also tests for Unicode
support are now part of the yaql
* Traces of execution were logged not as Unicode strings. Because
those traces contain parameter values ant function return value
logging failed when any of above contained non-ASCII chars
* Stack trace logging failed when frame expression contained
non-ASCII chars
* Exception messages could not contain non-ASCII chars
Also Logging API was not Unicode ready
Change-Id: Ief0b45f15669c5f8ee74fd6ff41fa5bc39c9500b
Closes-Bug: #1494275
9e8cec8910