Split error handling documentation by version for .NET 9/10 moniker ranges (#36040)

* Initial plan

* Create error-handling9.md include and add SuppressDiagnosticsCallback documentation

Co-authored-by: tdykstra <1569635+tdykstra@users.noreply.github.com>

* Fix invalid include path in error-handling9.md

Co-authored-by: tdykstra <1569635+tdykstra@users.noreply.github.com>

* Revert SuppressDiagnosticsCallback changes keeping only version split

Co-authored-by: tdykstra <1569635+tdykstra@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: tdykstra <1569635+tdykstra@users.noreply.github.com>

Author: Copilot

aspnetcore/fundamentals/error-handling.md

@@ -12,7 +12,7 @@ uid: fundamentals/error-handling
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-:::moniker range=">= aspnetcore-9.0"
+:::moniker range=">= aspnetcore-10.0"
 
 This article covers common approaches to handling errors in ASP.NET Core web apps. See also <xref:fundamentals/error-handling-api>.
 
@@ -343,8 +343,10 @@ An alternative approach to generate problem details is to use the third-party Nu
 * <xref:test/troubleshoot-azure-iis>
 * <xref:host-and-deploy/azure-iis-errors-reference>
 * <xref:fundamentals/error-handling-api>
+* [Breaking change: Exception diagnostics are suppressed when `IExceptionHandler.TryHandleAsync` returns true](https://github.com/aspnet/Announcements/issues/524)
 
 :::moniker-end
 
+[!INCLUDE[](~/fundamentals/error-handling/includes/error-handling9.md)]
 [!INCLUDE[](~/fundamentals/error-handling/includes/error-handling8.md)]
 [!INCLUDE[](~/fundamentals/error-handling/includes/error-handling3-7.md)]