Don't report a interp->native transition when it is done from a pinvoke method

[BrzVlad]

We didn't report these transitions when they were triggered from ILStubs because they already explicitly do this. Following the change of using transient IL belonging to the actual PInvoke method rather than separate ILStub methods (which should contain the same logic as the ILStub used to), we would now report the same event twice. We need therefore to also ignore the case where we are doing a PInvoke call from an actual PInvoke method.

Fixes src/tests/profiler/transitions/transitions.csproj which regressed after #126509 on interpreter.

[BrzVlad]

/azp run runtime-interpreter

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli, @kg
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

This PR adjusts CoreCLR interpreter profiling transition reporting to avoid double-counting managed↔unmanaged transition events when the interpreter executes transient-IL-backed P/Invoke methods (post-#126509). This restores expected behavior for profiler transition tests by suppressing interpreter-side transition callbacks in cases where the P/Invoke body already performs the transition notifications.

Changes:

• Suppress ProfilerManagedToUnmanagedTransitionMD / ProfilerUnmanagedToManagedTransitionMD callbacks in the interpreter calli-with-transition path when the currently interpreted method is a P/Invoke.
• Preserve the existing suppression for IL stubs, extending it to P/Invoke methods now that the transient IL is attributed to the P/Invoke MethodDesc.