Persistent container creation should work for concurrent runs

[karolz-ms]

Problem

Tests (e.g. using Aspire) might want to create and share the same persistent container (e.g. a database with test data). If the tests are running concurrently, there is a race to create the container if it does not exist initially.

Container creation is a multi-step process, but our code is not resilient enough if multiple instances of DCP start to create the same container. The result usually is that one instance succeeds, while others fail, reporting the container as FailedToStart.

Additional notes and requirements

• If a persistent container is reused by specific application run, it needs to be connected to the network used by that run (and disconnected from it when the run ends).
• To fix this issue we might need to invest in better DCP data store first. See API v2 #9 for more on that.