Skills Management in Docker

[NeonDaniel]

Objective

Provide a method for developing skills against a Docker-installed core

Initial Implementation

• [x] Handle an extra "dev" skills directory (hard-coded /skills? extra dirs in config?)
• [x] Handle dependency installation before skill load (and reload?)
  • [x] Handle parsing dependencies from a skill directory (OSM?)
  • [x] Handle installation of dependencies before skills service starts

Other considerations

• How do we manage conflicting skill names?
• Will skills resolve other skills properly being in multiple directories (i.e. brands/coupons)

[NeonDaniel]

From discussion with @NeonJarbas :

• multiple skill directories are handled by ovos-core
• Dependency installation is potentially slow and should be handled prior to skills module load

[NeonDaniel]

Closed by #217, #209