[BUG] Task Statuses Under Dynamic Workflow Not Propagated to FlyteAdmin Database

### Describe the bug

We are experiencing an issue with a dynamic sub-workflow.

The workflow executed successfully and displays the correct input and output, but the task information is not visible in the Flyte Console UI. There're logs under the "Executions" tab and no "Task" tab.

All child tasks of the sub-workflow also executed successfully, as confirmed through wandb logging. However, despite their successful execution, the statuses of these child tasks are shown as `UNKNOWN` instead of `SUCCEEDED` in Flyte UI, and there is no input/output data displayed.

Querying the `flyteadmindb.task_execution` table does not yield any logs for the nodes in question. This inconsistency suggests that while the Flyte Console UI is consistent with the FlyteAdmin database, it does not accurately reflect the actual execution status.

### Expected behavior

FlyteAdmin's `task_execution` table should correctly reflect the statuses of these tasks, and the Flyte Console should accordingly display the status as `SUCCEEDED` instead of `UNKNOWN`.

The Flyte Console should also properly display task information and logs for the parent sub-workflow.

### Additional context to reproduce

- We are on Flyte 1.15 (flytekit 1.15.3)

### Screenshots

(p1) Flyte UI showing the dynamic sub-workflow (parent)'s information: missing execution logs and the task tab

(p2) Flyte UI showing the child tasks of the dynamic sub-workflow: status `UNKNOWN`

(p3) Querying FlyteAdmin database `task_execution` table shows no trace of the sub-workflow's node and its child nodes

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

- [x] Yes

### Have you read the Code of Conduct?

- [x] Yes