Automation Server should not crash if some bad operations are defined

When deploying bundles defining chains that reference operations that are not deploy, you can end up in a state where automation API becomes unusable :

• Server is unable to generate the definitions needed by the java automation client
• Server is unable to generate the documentation

Technically all this is caused by a bad configuration, however the server should be more resilient and just skip the faulty operations/chains.