V12.0.0/xunit v3 v4 bump

[gimlichael]

This pull request updates documentation and configuration for the xUnit hosting test infrastructure, clarifying lifecycle management of test fixtures, removing obsolete compatibility examples, and updating default behaviors in the documentation. It also includes minor Dockerfile and configuration cleanups. The most important changes are summarized below.

Documentation updates for fixture lifecycle and defaults:

• Updated documentation to clarify that ApplicationTestFactory and WebApplicationTestFactory now use ManagedApplicationFixture<TEntryPoint> and ManagedWebApplicationFixture<TEntryPoint> by default, making entrypoint-owned startup the standard path for both generic host and ASP.NET Core test scenarios. Explicit instructions are provided for when to use alternative fixture types. [1] [2] [3] [4] [5] [6] [7]
• Revised lifecycle documentation for both generic host and ASP.NET Core fixtures, removing references to the obsolete BlockingManaged variants from summary tables and clarifying their status as compatibility-only. [1] [2]

Removal of obsolete compatibility examples:

• Deleted example documentation files for BlockingManagedApplicationFixture<TEntryPoint> and BlockingManagedWebApplicationFixture<TEntryPoint>, reflecting their deprecated status and encouraging use of the managed fixture path. [1] [2]

Configuration and infrastructure updates:

• Added a .gitattributes file to enforce consistent line endings and provide merge/diff settings for various file types.
• Updated .docfx/Dockerfile.docfx to use codebeltnet/docfx:2.78.5 (was 2.78.4), ensuring the latest documentation tooling is used.

Minor documentation and config cleanups:

• Removed the CA1200 rule suppression and the IDE0330 suppression from .editorconfig and fixed a typo in a comment. [1] [2]

These changes modernize the documentation, clarify recommended usage patterns, and clean up deprecated paths and configuration.

[greptile-apps]

Greptile Summary

The PR upgrades the repository to xUnit v4 and Microsoft.Testing.Platform, revises managed fixture startup behavior, removes obsolete blocking application fixtures, and updates supporting packages and documentation.

• Defaults application and web application test factories to managed fixtures.
• Adjusts deferred host startup synchronization and related functional tests.
• Updates package versions, test-runner configuration, release notes, and lifecycle documentation.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains.

No blocking failure remains.

Important Files Changed

Filename	Overview
src/Codebelt.Extensions.Xunit.Hosting/Internal/DeferredHostBuilder.cs	Revises deferred host startup completion ordering for managed fixture lifecycle handling.
src/Codebelt.Extensions.Xunit.Hosting/ApplicationTestFactory.cs	Changes the generic application test factory to use the managed application fixture by default.
src/Codebelt.Extensions.Xunit.Hosting.AspNetCore/WebApplicationTestFactory.cs	Changes the web application test factory to use the managed web application fixture by default.
Directory.Packages.props	Upgrades xUnit, test SDK, Codebelt, and coverage dependencies for the major release.
global.json	Selects Microsoft.Testing.Platform as the repository test runner.

Sequence Diagram

sequenceDiagram
  participant Test
  participant Factory
  participant ManagedFixture
  participant EntryPoint
  participant DeferredHost
  Test->>Factory: "Create<TEntryPoint>()"
  Factory->>ManagedFixture: Use default managed fixture
  ManagedFixture->>EntryPoint: Run application entry point
  EntryPoint->>DeferredHost: Build and publish host
  Test->>DeferredHost: Consume test host
  DeferredHost->>DeferredHost: Complete startup
  DeferredHost-->>Test: Started host and services

Loading

_{Reviews (4): Last reviewed commit: "💬 update changelog for v12.0.0" | Re-trigger Greptile}

[greptile-apps]

Analyzer comment spelling error

The edited rationale spells “because” as “becuase,” reducing the clarity of the repository-wide analyzer configuration.

Suggested change

	# Excluded becuase of inconsistency with other analyzers
	# Excluded because of inconsistency with other analyzers

Prompt To Fix With AI

This is a comment left during a code review.
Path: .editorconfig
Line: 174

Comment:
**Analyzer comment spelling error**

The edited rationale spells “because” as “becuase,” reducing the clarity of the repository-wide analyzer configuration.

```suggestion
# Excluded because of inconsistency with other analyzers
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!