Handling externally available strategies

[Treesarj]

currently, there is no way to know, the name of the strategy or find the strategy unless it is locally available. we need to add a new parameter to all strategies such that the pipeline can find the required strategy.

raised by @quaat

[CasperWA]

If what is meant here is to figure out what plugin package to install in order to support certain strategies, then that is a known issue when using plugins. One way is to make the plugin package a part of the metadata for a relevant part of the configuration. To begin with, we could (at least) have a registry of known/available plugins.