Added tests for UTF-8 validity of option values.

So far tests of the API and the set command checked only for ASCII values. Usage of UTF-8 should lead to no probems. The usage of UTF runes in the test value verifies this.
A clearer wording might be: 

Option values may be any UTF-8 encoded string. UTF-8 is accepted on the command line and in configuration files.