feat/pipeline_plugins

[JarbasAl]

• make the pipeline components plugins so they can be shipped in external packages, continuation of feat/pipeline #336
• needs new intent service/pipeline api ovos-utils#193
• needs feat/pipeline_plugins ovos-plugin-manager#177
• TODO needs changes in workshop around intent name munging

deprecations:

• move adapt bus handlers from IntentService to adapt plugin
• move padatious bus handlers from IntentService to padatious plugin
• subclass all services from plugins (converse/fallback/common_qa)
• add backward compatible properties with deprecation logs
• keep old handlers around with deprecation logs in case some downstream is calling them directly

plugins:

• exact matches heuristics plugin (including keyword intents) - feat/pipeline_plugins ovos-classifiers#22
• adapt plugin https://github.com/OpenVoiceOS/ovos-intent-plugin-adapt
• padacioso plugin -> shipped directly in padacioso lib since its under OVOS org feat/pipeline_plugin padacioso#20
• padatious plugin https://github.com/OpenVoiceOS/ovos-intent-plugin-padatious
• padaos plugin -> subset of padatious, only exact matches https://github.com/OpenVoiceOS/ovos-intent-plugin-padaos
• regex plugin -> pure regex intents, mk2 style https://github.com/OpenVoiceOS/ovos-intent-plugin-regex/
• jurebes plugin -> shipped directly in jurebes lib since its under OVOS org feat/pipeline_plugins jurebes#1
• persona plugin -> shipped directly in persona repo since its under OVOS org
• OOV framework proposal: OOVSkills #273
• nebulento plugin -> dead simple fuzzy match based intent engine feat/pipeline_plugin OpenJarbas/nebulento#1
• palavreado plugin -> dead simple keyword based intent engine feat/pipeline_plugin OpenJarbas/palavreado#1

core plugins (part of ovos-core):

• converse
• common_qa
• common_play (TODO - simplify OCP and add a component to handle OCP queries instead of relying in a registered intent via OCP plugin)
• fallback

pipeline considerations:

• need at least 1 of adapt/exact for keyword intents (adapt in classic mycroft)
• need at least 1 of padatious/padacioso/jurebes/padaos/exact for utterance intents (padatious in classic mycroft)
• exact_matches can work as a slower replacement to adapt bundled in ovos-classifiers (a direct dependency) -> adapt now fully optional
• padacioso can work as a slower replacement to padacioso (a direct dependency) -> padatious now fully optional
• for exact matches only, padaos should perform better than exact or padacioso
• pure regex intents, mk2 style -> new decorator needed in ovos-workshop to support registering these intents -> currently needs skills to emit bus events directly -> avoid plugin for now