docs(devServerStatus): Add Troubleshooting for invalid vscode setup resulting in DevServer not succeeding to connect

[DevTKSS]

GitHub Issue: closes #

PR Type:

• 📚 Documentation content changes

What is the current behavior? 🤔

If we are using a /src nested Repo layout, but not moved the .vscode/ contents also, the Uno Extension in vs code and also the DevServer dotnet tool doesn't connect to our app for debugging

• DevServer and Uno Platform Status not connected, but missing information and advised what we should do then
• uno-devserver start is failing in this case too

What is the new behavior? 🚀

doing the added advises solved this problem on my side

PR Checklist ✅

Please check if your PR fulfills the following requirements:

• [x] 📝 Commits must be following the Conventional Commits specification.
• [ ] 🧪 Added Runtime tests, UI tests, or a manual test sample for the changes have been added (for bug fixes / features) (if applicable)
• [x] 📚 Docs have been added/updated which fit documentation template (for bug fixes / features)
• [ ] 🖼️ Validated PR Screenshots Compare Test Run results.
• [x] ❗ Contains NO breaking changes

Other information ℹ️

@Jen-Uno Would you check if this might fix the problem for the other user too?

• https://github.com/unoplatform/uno/issues/21990
• the DevServer command --port might be not supported, commeded this out (so CI will potentially fail) please check this 👍

[unodevops]

⚠️⚠️ The build 185715 has failed on Uno.UI - docs.

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21998/docs/index.html