Bring managed cDAC process APIs in line with newer contract expectations

[Copilot]

Description

The managed cDAC reader was missing process-side implementations for several IXCLRDataProcess entry points that the newer contract surface expects. This change brings that path back in line so diagnostics scenarios can enumerate and resolve app domains, modules, and tasks through the managed reader without falling back to incomplete behavior.

• Implemented app-domain enumeration and lookup by unique ID.
• Implemented module enumeration and address-based module resolution using the current loader contracts.
• Implemented task lookup by unique ID and address-type classification for managed/runtime code addresses.
• Added and updated unit coverage for the affected IXCLRDataProcess behaviors.

Customer Impact

Without this, cDAC consumers using the managed reader can fail to enumerate or resolve core runtime objects such as app domains, modules, and tasks, which breaks diagnostics and inspection scenarios that depend on these APIs.

Regression

This fixes a regression in the managed cDAC implementation path after the IXCLRDataProcess surface was expanded to include these behaviors.

Testing

Covered by the managed cDAC unit test suite for IXCLRDataProcess, including app-domain, module, task, address-type, and related behavior tests.

Risk

Low. The change is localized to the managed cDAC IXCLRDataProcess implementation and is exercised by the existing cDAC unit tests.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

[Copilot]

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

[azure-pipelines]

Azure Pipelines:
Successfully started running 4 pipeline(s).
11 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.