set STT response encoding to utf-8 (deepspeech local)

[nutzl]

Description

Setting STT response encoding to utf-8 for local deepspeech server, by setting encoding attribute of urllib-response to utf-8 to omit encoding auto-detection, that fails sometimes.

How to test

Use Mycroft with local deepspeech server with German language model: umlauts aren't encoded correctly and therefore response is not understood.

Contributor license agreement signed?

CLA [x] (Whether you have signed a CLA - Contributor Licensing Agreement

[devops-mycroft]

Hello, @nutzl, thank you for helping with the Mycroft project! We welcome everyone
into the community and greatly appreciate your help as we work to build an AI
for Everyone.

To protect yourself, the project, and users of Mycroft technologies we require
a Contributor Licensing Agreement (CLA) before accepting any code
contribution. This agreement makes it crystal clear that along with your
code you are offering a license to use it within the confines of this project.
You retain ownership of the code, this is just a license.

Please visit https://mycroft.ai/cla to initiate this one-time signing. Thank
you!

[devops-mycroft]

Voight Kampff Integration Test Succeeded (Results)

[krisgesling]

Hey there, thanks for helping to improve Mycroft!

Would you be able to see if the Content-Type header of the response contains the charset value of "utf-8"?

If it does then we could use that value, which should work in the event that the response is not UTF-8 encoded.

Any opinions from those reading along on whether this is a concern or likely?