migrate STT to ovos plugin manager

[JarbasAl]

now all ovos plugins can be used with local backend for STT

the same should be done in the future for TTS

[ChanceNCounter]

The only good way to test this repo is to build OVOS.

[JarbasAl]

or just launch the repo in any device at all and point some mycroft.conf to it?

[ChanceNCounter]

That works sometimes. Perhaps most of the time. It doesn't work when a lib's system deps have changed, and, in this case, it doesn't tell us about first-run.

That's a good way to see what happens when you upgrade in place, though.

[JarbasAl]

tested in laptop, ovos and bigscreen, self merging

2021-10-21 07:12:36.625 - OVOS - ovos_plugin_manager.stt:create:64 - INFO - Loaded the STT plugin ovos-stt-plugin-chromium
 * Serving Flask app 'ovos_local_backend.backend' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
07:12:36.728 - werkzeug - INFO -  * Running on http://127.0.0.1:6712/ (Press CTRL+C to quit)
07:12:59.790 - werkzeug - INFO - 127.0.0.1 - - [21/Oct/2021 07:12:59] "GET /v1/device//subscription HTTP/1.1" 308 -
07:12:59.801 - werkzeug - INFO - 127.0.0.1 - - [21/Oct/2021 07:12:59] "GET /v1/device/subscription HTTP/1.1" 200 -
07:22:30.883 - werkzeug - INFO - 127.0.0.1 - - [21/Oct/2021 07:22:30] "POST /v1/stt?lang=en-US&limit=1 HTTP/1.1" 200 -
07:22:55.307 - werkzeug - INFO - 127.0.0.1 - - [21/Oct/2021 07:22:55] "POST /v1/stt?lang=en-US&limit=1 HTTP/1.1" 200 -