feat: support to subflows on the Java DSL

[matheusandre1]

Many thanks for submitting your Pull Request ❤️!

What this PR does / why we need it:
Closes: #1151

Special notes for reviewers:

Additional information (if needed):

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[mcruzdev]

It looks great @matheusandre1, could you add a test running a workflow with your changes?

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[ricardozanini]

Looks solid, we just need to add the Function to the input or it's useless for the FuncDSL (unless jq scripting).

[fjtirado]

Looks solid, we just need to add the Function to the input or it's useless for the FuncDSL (unless jq scripting).

@ricardozanini The Function should be located at the experimental module, I think it can be another PR.

[ricardozanini]

Indeed, the Function can be added to a new PR - or directly to this one. Not sure why not. I do the DSL changes in both sides all the time since one influence the other.

[matheusandre1]

@mcruzdev aproove?

[mcruzdev]

Hi @matheusandre1, when a said test I would like something like FuncDSLDataFlowTransformationHelpersTest#test_input_with_outputAs.

Executing the new DSL method with a WorkflowApplication:

    try (WorkflowApplication app = WorkflowApplication.builder().build()) {
      WorkflowDefinition def = app.workflowDefinition(workflow);

      WorkflowModel model = def.instance(10L).start().join();
      Number number = model.asNumber().orElseThrow();

      softly.assertThat(number.longValue()).isEqualTo(25L);
    }

The test you added is so good, but I think we need to test executing too.

[matheusandre1]

I'm going to do it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[mcruzdev]

Hi @matheusandre1, it is close. You need to test what you added here. Instead use the enrichOutputWithTaskTest workflow use that one you added on testDoTaskRunWorkflow test:

    Workflow wf =
        WorkflowBuilder.workflow("parentFlow")
            .tasks(
                d ->
                    d.workflow(
                        "runChild",
                        w ->
                            w.namespace("org.acme")
                                .name("childFlow")
                                .version("1.0.0")
                                .input(Map.of("id", 42, "region", "us-east"))
                                .await(false)
                                .returnType(RunTaskConfiguration.ProcessReturnType.NONE)))
            .build();

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[fjtirado]

You can remove that catch and use join rather than get
In any case, rather than catching and trowing runtime, you can declara that the test function throw any checked exception that might be raised by the code within the function

[matheusandre1]

ok, understand, thank you

[fjtirado]

you can change to assertThat() and remove the call toString