This should allow lldb-server to operate on files with non-ascii pathnames.
I tried looking around in lldb/tools, and this seemed like the only other tool (other than the main lldb driver itself) that would be used (implicitly) by an end user (which could be working in non-ascii paths).
This does the same as for D68770 (where the main driver earlier was using custom code in the driver to convert unicode to utf8), while lldb-server didn't have any unicode handling at all before (where the main arguments would be given in the native local codepage, while the rest of llvm internals expect utf8).