Is your feature request related to a problem?

Mostly people are out of trouble with WSL2 if they use the Windows installer, but sometimes they do get into trouble, as in

• Https not working with v1.25 (Windows, Firefox) #8189

They can also get in trouble if they use an unsupported browser (firefox on windows) or if they use the WSL2 browser (linux-side Chromium for example).

It happens with non-WSL2 as well. People may be missing the mkcert -install or may need to ddev poweroff && mkcert -uninstall && rm -rf "$(mkcert -CAROOT)" && mkcert -install && ddev start

Describe your solution

1. Build a diagnoser tool for WSL2.

• See steps in Https not working with v1.25 (Windows, Firefox) #8189 (comment)
• Verify WSL2 network type
• Verify port mappings
• Verify environment variables
• Explain CAROOT situation
• Add docs that explain the things explained in Https not working with v1.25 (Windows, Firefox) #8189 (comment)
• Use direct tools to validate use of proper CA both on Windows and in WSL2.

2. Improve blogs on ddev.com/blog and perhaps in our docs to explain how the magic works on WSL2

Related:

• Feature Request: ddev utility port-diagnose #8085

Describe alternatives

No response

Additional context

No response