Add ContainerRuntimeInitializationTimeout to abort startup when container runtime stays unhealthy for too long

[ReubenBond]

Description

In integration testing scenarios, there is typically no human operator around to monitor the dashboard to observe and fix transient errors such as the container runtime (eg, docker or podman) being unavailable. Currently, tests will hang in these cases. This PR addresses this by adding a new TimeSpan property DcpOptions.ContainerRuntimeInitializationTimeout (default 10s), accessible by configuring DcpPublisher:ContainerRuntimeInitializationTimeout.

Fixes #6790

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).