Add WSL-specific Podman documentation and troubleshooting guide

[Copilot]

This PR addresses a common issue where .NET Aspire applications fail to find Podman in Windows Subsystem for Linux (WSL) environments, even when Podman commands work correctly in the terminal.

Problem

Users encounter the error:

Container runtime 'podman' could not be found. The error from the container runtime check was: exec: "podman": executable file not found in $PATH

This occurs in WSL environments where:

• Podman is installed in a separate WSL distribution
• Users rely on shell aliases (like alias podman='podman-remote-static-linux_amd64' in ~/.bash_aliases)
• The podman executable isn't directly available in the system PATH

Solution

The PR adds comprehensive documentation to help users properly configure Podman in WSL environments:

1. Enhanced Container Runtime section in setup-tooling.md with WSL-specific considerations explaining:

   • Why shell aliases don't work with .NET Aspire's executable resolution
   • Solutions for cross-distribution Podman setups
   • Proper PATH configuration and symbolic link alternatives
   • Verification steps

2. New troubleshooting document podman-wsl-not-found.md following the standard troubleshooting template pattern with:

   • Clear error symptoms and root cause analysis
   • Multiple solution approaches (local installation, symbolic links, PATH modification)
   • Step-by-step verification instructions
   • WSL-specific considerations

3. TOC entry added to make the troubleshooting guide discoverable in the documentation navigation

4. Cross-references added to connect users to the troubleshooting guide from relevant documentation sections

The documentation clearly explains that .NET Aspire resolves container runtimes by searching the system PATH for executables, and shell aliases aren't recognized during this process.

Fixes #1651.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

---

Internal previews

📄 File	🔗 Preview link
docs/fundamentals/setup-tooling.md	docs/fundamentals/setup-tooling
docs/get-started/migrate-from-docker-compose.md	docs/get-started/migrate-from-docker-compose
docs/toc.yml	docs/toc
docs/troubleshooting/podman-wsl-not-found.md	docs/troubleshooting/podman-wsl-not-found

[IEvangelist]

We need a TOC entry for this new article.

[IEvangelist]

Hey @copilot, we need a TOC entry for this new article. Also, can this article be written according to the troubleshooting template at https://review.learn.microsoft.com/en-us/help/patterns/level4/global-problem-resolution-template?branch=main

[Copilot]

We need a TOC entry for this new article.

Added TOC entry for the new troubleshooting article. The entry is placed in the troubleshooting section near other container runtime related articles. Commit a0a76b1.

Hey @copilot, we need a TOC entry for this new article. Also, can this article be written according to the troubleshooting template at https://review.learn.microsoft.com/en-us/help/patterns/level4/glo...

Added TOC entry and restructured the article according to the troubleshooting template pattern. The article now follows a more concise structure with clear Symptoms, Cause, Solution, and verification sections similar to other troubleshooting articles in the docs. Commit a0a76b1.

[adegeo]

@copilot rewrite this article according to the template at https://review.learn.microsoft.com/en-us/help/patterns/level4/global-problem-resolution-template?branch=main

Make sure to set the appropriate topic type metadata.