Setup (with SetupBuildingScenario) fails intermittently due to eventually consistency of datastore

Initializing a new ADT instance using `SetupBuildingScenario` can sometimes fail because of the eventual consistency in the backing datastore.

I tried a few times today and saw different errors at different points:

1. sometimes, it claims that fields on the twin are not valid according to the model, despite the model having them (it seems the model was created, but not yet made available by backend yet so it thought the fields didn't exist)
2. other times, the initial twin creation was successful but creating the relationships failed, claiming the twins did not exist yet (despite just having been created).

In either case, if I captured the net-traces using tools like `mitmproxy`, re-running the same REST call a few seconds later worked.

I suggest the sample introduce small delays between model creation, twin creation, and relationship creation to avoid this.

Locate the SetupBuildingScenario initialization flow in the sample and trace the calls that create the model, twins, and relationships. Reproduce the intermittent failures and compare them with retries after a short wait. Done means a fresh ADT instance can be initialized reliably without model-availability or missing-twin errors.

Written by the indexing model from the issue text.