[BUG] 1.3.0 broke task execution

[honnix]

Describe the bug

After upgraded to 1.3.0, remote.execute stopped working with exception:

...
                # We need to manually make a map of the nodes since there is none for single task executions
                # Assume the first one is the only one.
                node_mapping = (
                    {
>                       task_node_exec[0].id.node_id: FlyteNode(
                            id=flyte_entity.id,
                            upstream_nodes=[],
                            bindings=[],
                            metadata=NodeMetadata(name=""),
                            flyte_task=flyte_entity,
                        )
                    }
                    if len(task_node_exec) >= 1
                    else {}  # This is for the case where node executions haven't appeared yet
                )
E               TypeError: __init__() got an unexpected keyword argument 'flyte_task'
.tox/py38-test/lib/python3.8/site-packages/flytekit/remote/remote.py:1454: TypeError

As commented in flyteorg/flytekit#1348 (comment), it seems to be that PR breaking it during refactoring.

Expected behavior

remote.execute should work

Additional context to reproduce

• Upgrade to 1.3.0
• Do the following

execution = remote.execute(
        ...
    )

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[kumare3]

this sounds, odd, pyflyte run uses this same code path. Checking!

[kumare3]

ohh i see it, its in sync execution. so the wait is broken?

[wild-endeavor]

flyteorg/flytekit#1422