Add ability to parse other text encodings to tail/logparser input

Relevant telegraf.conf:

[[inputs.logparser]]
files = ["C:\\Users\\jen.tomm\\Desktop\\applicationlog_2019-11-13_07-43-25\\sample.log"]
from_beginning = false
[inputs.logparser.grok]
measurement = "applicationlog"
patterns = ["^%{TIMESTAMP_ISO8601:timestamp},%{WORD:LogLevel},%{NUMBER:ThreadId},%{WORD:LoggerName},%{DATA:ServiceId},%{DATA:RequestId},%{DATA:UserId},%{DATA:RemoteDate},%{DATA:RemoteServer},%{DATA:RemoteProcessId},%{DATA:RemoteThreadId},%{GREEDYDATA:message}"]
### System info:
windows
telegraf 1.13

### Steps to reproduce:

1. parsing logs through log parser with grok pattern
2. using grafana log panel plugin to get the log metrics

### Expected behavior:

logs have to display with proper format but getting space between the letters

### Actual behavior:

getting space between the logs

2 0 1 9-1 1-1 3 0 4 : 5 4 : 5 4 . 8 6 1 0 0 0 , D E B U G, 6 1 0 0 , a p p
l i c a t i o n S e r v i c e , R e n d e r W o r k e r , , , , , , , " R e n d e r Q u e u e H a n d l e r _ R e a d B o d y : W o r k e r < E U D - V - 0 A 6 F 5 5 1 8 _ 0 > r e q u e s t < G e t J o b > "

### Additional info:

Date,LogLevel,ThreadId,LoggerName,ServiceId,RequestId,UserId,RemoteDate,RemoteServer,RemoteProcessId,RemoteThreadId,Message
2019-11-13 04:54:54.861000,DEBUG,6100,applicationService,RenderWorker,,,,,,,"RenderQueueHandler_ReadBody: Worker request "
2019-11-13 04:54:54.920000,NOTICE,4592,applicationService,EUD-V-0A6F55180|55ECC331,,jen.tomm,,,,,"QueueHandler::GrowServicePoolThreads: Growing thread pool count to <9>"

Start with the tail/logparser input configuration and reproduce the Windows sample.log case using the provided Grok pattern. Identify how the input currently handles text encoding; done means supported non-default encodings parse without spaces between characters and the resulting logs display in the proper format.

Written by the indexing model from the issue text.