New maintainers / proposed archiving of neotest-dotnet

[Issafalcon]

Context

While I started this adapter with enthusiasm, and more importantly, plenty of free time, my circumstances have changed (in a wonderful, but increasingly demanding childcare kind-of-way), so my ability to jump into solving issues, investigating problems, and general maintenance has been significantly diminished.

I have also come to realise that maintaining this adapter using it's current approach to test discovery, supporting multiple .NET testing frameworks, is an impossible task, even with unlimited time to spend. This is due to the nature of how different each framework actually behaves and interacts with the .net test runner.

Next steps

While I appreciate all the issues raised, and pull requests submitted, I believe that further efforts into continuing with this approach to maintaining all the possible iterations of treesitter querying and parsing of dotnet tests results, is not the most efficient way forward. Instead, leveraging the vstest platform like in neotest-vstest should be where efforts are forwarded.

I can't say that the vstest adaptor will satisfy all use cases, and in many instances, this adapter may work better (I still use it for the majority of my xUnit testing in neovim), but with community support, I think it will become a much more robust and maintainable solution going forward.

That said, if anyone would like to tackle the challenge of maintaining this adapter as it stands, I will welcome a change of hands. Otherwise, I will eventually archive this adapter.