Updated test framework package references to latest

[clrudolphi]

🤔 What's changed?

Modified the New Project wizard configuration to reference the latest versions of the test execution frameworks.

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[Copilot]

Pull request overview

Updates the Visual Studio “Reqnroll Project” template to generate new projects referencing newer versions of supported test frameworks and their runners/adapters.

Changes:

• Bumped Reqnroll test-framework integration packages (xUnit, xUnit.v3, NUnit, MSTest, TUnit) to newer versions.
• Updated underlying test framework / runner / adapter package versions (xunit.runner.visualstudio, xunit.v3, NUnit, NUnit3TestAdapter, MSTest, TUnit).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[304NotModified]

I see the tests are broken on main. I don't if this is the result of merging this PR

@clrudolphi any idea? I havent found time to check the root cause of the test failures

[clrudolphi]

I see the tests are broken on main. I don't if this is the result of merging this PR

@clrudolphi any idea? I havent found time to check the root cause of the test failures

The connector tests are dynamically building a few of the Reqnroll example sample projects from the ReqnrollExploratoryTestProjects repo, such as the SpecFlowCompatibilityProject. Those projects have hard-wired references to Reqnroll 3.3.4-local:

 		<PackageReference Include="Reqnroll.SpecFlowCompatibility" Version="3.3.4-local" />

Version 3.3.4 final was released two days ago and so a reference to 3.3.4-local isn't valid.
I am not sure whether those should be updated to the latest released build or to a local build of version 4.0.0 (the next build coming).