Log container runtime unhealthy or missing as warning

[JamesNK]

Description

After:

Fixes #6655

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

[JamesNK]

Here is what it looks like with error instead:

Thinking about this more, I like error as the level.

• Critical = app will crash and exit
• Error = wrong and broken
• Warning = wrong but you can ignore if you want

If you have an app with a container, and the container isn't running, your app most likely is in an error state. You must start the container runtime for all your resources to run.