Allow deleted containers to be restarted

[JamesNK]

Description

Fixes #5977

I tested that a container resource with a deleted container will successfully restart.

I think there is a follow up improvement in DCP to give a better state than Unknown in this situation.

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]

Why not fix in dcp? Is this podman only? It only applies for containers right

[JamesNK]

What would the fix be in DCP? If a container is deleted in container tooling then DCP automatically recreates the container? That feels a little too magical to me.

Ideally I think DCP reports a clear status, and then someone has the option to press start on the resource if they want. If DCP has a new status then app host will need to react to it. Basically the exact same thing I did here with Unknown.

[karolz-ms]

Exposing "Start" for Containers in Unknown state a good bet in general. In future might have a specific state for Container objects that had corresponding Docker/Podman containers deleted, but that is not really a mainline scenario.

[JamesNK]

Follow up issue to improve state from DCP: #7287