When checking the openapi file that's been generated for a running serverless workflow (checking at http://localhost:8080/q/openapi) I can see that all the path operations don't contain the `operationId` attribute. So we can have a path with more than one operation (get/post...) and there's no way to identify the operation.

In SWF Editor Catalog we use the `operationId` attribute to be able build function definitions from openapi files. Without it we may not be able to correctly identify the function definitions when dealing with SWF openapi's.