Arguments mapping is very verbose depending on use case

[flaviuvadan]

Is your feature request related to a problem? Please describe.
It sucks to write

func1 = my_func1(...)
func2 = my_func2(
    arguments={'a': func1.get_parameter('a').value, 'b': func2.get_parameter('b').value}   # <<<<<<<<
)

Describe the solution you'd like
Something that allows clients to write

func1 = my_func1(...)
func2 = my_func2(
    arguments=func1.outputs  # <<<<<<<<
)

Hera can, by default, assume that users want to map all the output parameters from func1 to func2

CC: @ljyanesm

[elliotgunton]

@flaviuvadan / @samj1912 this looks like a good improvement we should do for the new decorators - currently this isn't possible:

class PassthroughIO(Input, Output):
    my_str: str
    my_int: int
    my_artifact: Annotated[str, Artifact(name="my-artifact", loader=ArtifactLoader.json)]


@w.script()
def give_output() -> PassthroughIO:
    return PassthroughIO(my_str="test", my_int=42)


@w.script()
def take_input(inputs: PassthroughIO) -> Output:
    return Output(result=f"Got a string: {inputs.my_str}, got an int: {inputs.my_int}")


@w.dag()
def my_dag():
    output_task = give_output()
    take_input(output_task)

As you have to do

    take_input(
        PassthroughIO(
            my_str=output_task.my_str,
            my_int=output_task.my_int,
            my_artifact=output_task.my_artifact,
        )
    )

[sambhav]

Makes sense to me