Java defined WFs tasks are serialized without the `call` field

[fantonangeli]

What happened:
Workflows defined through the Java SDK are serialized without the call field.

As a result, the TypeScript SDK returns the following error:

Unable to defined task type of task named 'findPetByStatus'

The generated task contains this:

{
  "findPetByStatus": {
    "with": {
      "document": {
        "endpoint": "openapi/petstore.json"
      },
      "operationId": "findPetsByStatus",
      "parameters": {
        "status": "sold"
      }
    }
  }
}

The serialized task should also contain:

"call": "openapi"

Example:

{
  "findPetByStatus": {
    "call": "openapi",
    "with": {
      "document": {
        "endpoint": "openapi/petstore.json"
      },
      "operationId": "findPetsByStatus",
      "parameters": {
        "status": "sold"
      }
    }
  }
}

What you expected to happen:
OpenAPI tasks defined through the Java SDK should be serialized with:

"call": "openapi"

The resulting workflow should be valid according to the DSL and should be correctly recognized by the TypeScript SDK.

How to reproduce it:
Use the Quarkus Flow Petstore example:

https://github.com/quarkiverse/quarkus-flow/tree/main/examples/petstore-openapi

1. Run the petstore-openapi example.

2. Open:

   http://localhost:8080/q/dev-ui/quarkus-flow/workflows
   

3. Open the workflow diagram by clicking the eye icon.

4. Observe that the diagram cannot be rendered and the TypeScript SDK reports:

   Unable to defined task type of task named 'findPetByStatus'
   

Anything else we need to know?:
This deployment of the DiagramEditor can be used for a final check to test that the generated workflow is accepted by the typescript-sdk:
https://deploy-preview-274--openworkflow-editor.netlify.app/?path=/story/diagram-editor--component

Environment:

• Specification version used: 1.0.0

[fantonangeli]

cc @ricardozanini @fjtirado