[release/10.0] [Blazor] OwningComponentBase Dispose method in .NET 10 gets back the original behavior

[github-actions]

Backport of #64695 to release/10.0

/cc @javiercn @ilonatommy

Restore Dispose(bool disposing) with disposing=true on async disposal for Blazor components.

Description

In .NET 9, disposing a Blazor component would call IDisposable.Dispose(), which then invoked Dispose(bool disposing) with disposing=true. This allowed user overrides of Dispose(bool disposing) to execute necessary cleanup logic for managed resources. However, in .NET 10, after introducing IAsyncDisposable support (PR #62583), the framework began invoking IAsyncDisposable.DisposeAsync(), which followed the typical .NET dispose pattern and called Dispose(false). This caused user code that depended on disposing=true to break, as DisposeAsync() was now incorrectly signaling a non-disposing context.

This fix ensures backward compatibility by making DisposeAsync() call Dispose(true), just as in .NET 9 and earlier. Additionally, the IsDisposed = true assignment has been removed from DisposeAsyncCore(), and its handling is now consolidated within Dispose(bool disposing) for consistency and to prevent double-disposal.

Fixes #64669

Customer Impact

Without this fix, users overriding Dispose(bool disposing) in Blazor components could see their cleanup logic silently skipped in .NET 10, leading to resource leaks or unexpected behavior. This change restores the expected contract and makes async disposal consistent and safe for component authors who rely on the documented pattern.

Regression?

• Yes
• No

Regressed from: .NET 9

Risk

• High
• Medium
• Low

This change restores prior contract and behavior; automated tests confirm idempotency and compatibility. Since the implementation centralizes disposal logic, risk of introducing regressions is low.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[neissljanik]

Hi, is there any ETA for when this PR will be merged? I understand the issue is still not fixed in .NET 10?

[neissljanik]

@javiercn @ilonatommy ?