Skip exporting mining outcome for disabled algorithms

[marekhorst]

Currently exporting phase is totally unaware of an algorithm status and whether given algorithm was enabled or disabled. Each algorithm produces an outcome regardless being disabled or enabled (empty outcome is produced in such case).

This may be confusing to the action manager subsystem which relies on a hierarchy of actionsets where the most recent actionset is picked even if it was generated by a disabled mining module (which is an empty actionset). Apparently this may become an issue in the new Action Manager implementation even though we didn't have problems with this approach in its previous version bound to an old DM cluster.

In order to avoid such confusion we should skip exporting an outcome for disabled module. This may require adding quite a lot of decision nodes (relying on active_${algo_name} flags) in IIS primary exporter subworkflow.

[marekhorst]

It turned out when the module is deactivated the (empty) rawset ID is not elected as the LATEST by the ActionManager.

Therefore we can lower the priority for this issue.