Fix: critical Bad request error from Wit.ai and Update: api url

[zoecarver]

When Wit.ai STT gets something it cannot parse into text it returns 400 Bad request. This is presented as a critical error when it does not need to be. This critical error is making people abandon jasper after getting so far.

This PR also updates the API version.

Issues this PR will fix

• INFO:client.stt:Transcribed: [u'JASPER'] CRITICAL:client.stt:Request failed with response: u'{\n "error" : "Bad request",\n "code" : "bad-request"\n}' Traceback (most recent call last): File "/home/pi/jasper/client/stt.py", line 594, in transcribe r.raise_for_status() File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 829, in raise_for_status raise HTTPError(http_error_msg, response=self) HTTPError: 400 Client Error: Bad Request CRITICAL:client.stt:Request failed with response: u'{\n "error" : "Bad request",\n "code" : "bad-request"\n}' Traceback (most recent call last): File "/home/pi/jasper/client/stt.py", line 594, in transcribe r.raise_for_status() File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 829, in raise_for_status raise HTTPError(http_error_msg, response=self) HTTPError: 400 Client Error: Bad Request #655
• Many Issues with Jasper Installation #648
• Default Wit-ai url is changed #650

Question

• With this PR, jasper logs 'Response: Failed to parse'. Should this be a warning? Should it not log anything?