The content creation generic setup import step used to depend on the "languagetool" import step which is actually defined by Products.PloneLanguageTool (not by plone.app.multilingual).
Products.PloneLanguageTool is no longer state of the art as we use p.a.multilingual now.
Thus we do no longer need the misleading dependency which did not work correctly anyway (the condition cannot work like that).
The content creation generic setup import step used to depend on the "languagetool" import step which is actually defined by Products.PloneLanguageTool (not by plone.app.multilingual).
Products.PloneLanguageTool is no longer state of the art as we use p.a.multilingual now.
Thus we do no longer need the misleading dependency which did not work correctly anyway (the condition cannot work like that).
Replaces #41