Description

Improve Rider IDE setup documentation and add troubleshooting guidance for TUnit test discovery issues caused by VSTest runner conflicts.

Changes:

• docs/docs/troubleshooting.md — Restructured the IDE Setup section into per-IDE subsections (Visual Studio, Rider, VS Code). Added Rider-specific troubleshooting for VSTest project name mask conflicts.
• docs/docs/getting-started/running-your-tests.md — Fixed missing quotes around "Enable Testing Platform support" in the Rider section.
• docs/static/img/rider.png — New screenshot.
• rider.png (root) — Removed orphan file that was not referenced anywhere in the project.

Related Issue

Addresses RIDER-129926 — Rider does not discover TUnit tests in projects named Tests.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Performance improvement
• Refactoring (no functional changes)

Checklist

Required

• I have read the Contributing Guidelines
• If this is a new feature, I started a discussion first and received agreement
• My code follows the project's code style (modern C# syntax, proper naming conventions)
• I have written tests that prove my fix is effective or my feature works

TUnit-Specific Requirements

N/A — documentation-only change, no code modifications.

Testing

N/A — documentation-only change.

Additional Notes

When a TUnit project name matches a VSTest project name filter (e.g. *Tests*), VSTest also claims the project. With the default "Ignore projects discovered by other test frameworks" option enabled, Testing Platform yields to VSTest, and TUnit tests are not discovered. The updated docs explain this conflict and provide two resolution paths: removing the VSTest filter (recommended) or disabling the "Ignore projects" option.