[release/10.0] Invoke members for dispatch interfaces on that interface's corresponding IDispatch pointer, not on the canonical one

[github-actions]

Backport of #122200 to release/10.0

/cc @jkoritzinsky

Customer Impact

• Customer reported
• Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Method call on an IDispatch-based ComImport interface fails to call the target COM method if the target COM object is a .NET object exposed to COM that uses the ClassDefaultInterfaceAttribute; instead, an exception is thrown.

Regression

• Yes
• No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Introduced in .NET 9

#104406

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Added a unit test to validate the scenario and validated that the repro no longer fails.

Risk

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

Low. Reverts the incorrectly functioning part of the regressing PR to the .NET 8 code path.

IMPORTANT: If this backport is for a servicing release, please verify that:

• For .NET 8 and .NET 9: The PR target branch is release/X.0-staging, not release/X.0.
• For .NET 10+: The PR target branch is release/X.0 (no -staging suffix).

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.