Fix: Resolve ambiguity in TryGetElementType() for Mono runtime (#3395)

[medhatiwari]

Summary

Fixes #3395

This PR addresses a discrepancy in the Mono runtime that adds extra generic interfaces, such as IEnumerable<int>, for arrays and collections. This behavior causes failures in the EFCore.PG test suite, particularly in the TryGetElementType() logic used for interface resolution.

@uweigand @giritrivedi @saitama951

[giritrivedi]

@roji
Can azure pipeline be run here to see if this workaround is not causing any regressions ?

[roji]

@giritrivedi I've triggered the CI, but I'm not sure it's appropriate to merge this rather than just having it fixed on the mono side. And by the way, this specific function is a copy-paste from the EF source code, so the same problem should exist there.

[giritrivedi]

Thanks @roji. We will work on giving a fix in Mono.

[roji]

@giritrivedi OK, that's great to hear! Are you OK with me closing this PR and #3395 then?

[giritrivedi]

I will let @uweigand comment on this.

[uweigand]

I agree the right thing is to fix this in the runtime (note this is about the Mono flavour of the dotnet runtime, not the classic Mono standalone project). However, it may take quite a bit of time for any runtime fix to actually become available in the official releases customers are using. Therefore, we were wondering if it would be acceptable to have a workaround in this project for the time being.

[giritrivedi]

@roji Can this be merged to ensure customers do not face this issue until a better fix is provide in Mono runtime ?

[medhatiwari]

Hi @roji,

As noted by @uweigand and @giritrivedi, the Mono runtime fix might take some time to be available in official releases. This workaround ensures customers are not impacted in the meantime. Since all checks have passed, would you agree to merge this PR as an interim solution while we continue working on the permanent fix in the Mono runtime?

Looking forward to your thoughts.