Swift: Finalize progressive rendering behavior of child lists

> It's not uncommon for 1) an `updateComponents` message to describe a component that reference other components as its children and 2) the client hasn't heard a thing about those children yet (that often arrives in a follow-up `UpdateComponents` message that comes right after the first).
>
> In this scenario, wouldn't the lookup return `nil` and every caller just drops its job of rendering this subtree because `resolveChildList` skips nil children.
>
> In this scenario, our prior art implements progressive rendering, putting placeholders in place of children that have yet to arrive. I don't remember off the top of my head how much better this tends to look compared to the more classical approach of just having components pop in as they arrive, so your mileage may vary.
>
>
>
>

_Originally posted by @andrewkolos in [#2052](https://github.com/a2ui-project/a2ui/pull/2052/changes/BASE..a2a3eb346038b0723b2289a3d03b0c2799e58654#r3639480312)_

Once the Basic Catalog and Sample App are up and running, finalize the behavior of declared but missing (or incomplete) render nodes. Perhaps with a placeholder view or perhaps pop-in.

L’issue fait référence au comportement de rendu progressif des listes enfants dans Swift. Commencez par examiner la fonction `resolveChildList` et la manière dont elle gère les enfants nil. Examinez Basic Catalog et Sample App pour comprendre le flux de rendu actuel. Déterminez s’il faut implémenter des placeholders ou du pop-in pour les nœuds de rendu manquants, puis testez le résultat visuel.

Rédigé par le modèle d'indexation à partir du texte de l'issue.