add support for mapping over remote launch plans

[pvditt]

Tracking issue

fixes: https://linear.app/unionai/issue/COR-1686/support-mapping-over-flytelaunchplan-remote

Why are the changes needed?

Mapping over remote launch plans doesn't work

What changes were proposed in this pull request?

• add support for mapping over remote launch plans by using create_and_link_node_from_remote
• updated models TypedInterface to transform variables of a type or variables of a collection of type

How was this patch tested?

• unit testing
• sandbox
• dogfood (https://dogfood-gcp.cloud-staging.union.ai/console/projects/flytesnacks/domains/development/executions/arqcgvlsbz92cdffsw2d/nodeId/n0/nodes)

Setup process

remote = UnionRemote(config=Config.auto(), default_project="flytesnacks", default_domain="development")
lp1 = remote.fetch_launch_plan(name="advanced_composition.subworkflow.regression_line_wf",
                               version="v0.3.288")


@workflow
def test_wf1_remote():

    val = [1, 2, 3]
    x = [[-3, 0, 3], [-8, 2, 4], [7, 3, 1]]
    y = [[7, 4, -2], [-2, 4, 7], [3, 6, 4]]
    map_task(lp1)(val=val, x=x, y=y)

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Docs link

[eapolinario]

Thanks for fixing this. Let's try to keep the interface clean by not using Any at this point, unless we have a very good reason.

[eapolinario]

Can we use Union to describe the types? I'd rather keep ArrayNode well-typed.

[pvditt]

yup - getting an update for this. Was working around a circular imports error. Can use if TYPE_CHECKING

[wild-endeavor]

I think there's some circular dependency that needs to happen but I think maybe what's here right now is more than necessary. let's chat about this some time today or tomorrow?