[release/7.0] Fix configuration binding with types implementing IDictionary<,>

[tarekgh]

Fixes #78938

Backport of #78946 to release/7.0

/cc @tarekgh

Customer Impact

This issue is reported by the app-compat runs when running mixcore/mix.core app. The app will throw System.Reflection.AmbiguousMatchException during the configuration binding. This is a regression from the fix #78118 we had in 7.0.1 servicing. This problem occur only if the app is using a type implementing IDictionary<,> and include members with the same names as IDictionary<,> members. Like class indexer this[] or TryGetValue method. When using such class with the configuration, we use the reflection to bind to such class using the type indexer and TryGetValue method. If there is multiple members with the same name, the reflection will throw AmbiguousMatchException.

Testing

I have tested the exact code used to repro the issue with the app-compat run with referencing the packages Quartz.AspNetCore v3.3.3 and Quartz.Extensions.DependencyInjection v3.3.3 which causing the problem. I have run all our tests against the fix which is covering all cases we fixed before to ensure no other regressions. Also, I have added extra test to catch the issue we are fixing here.

Risk

Medium, touching configuration code comes with some risk but I tried my best testing the change to ensure will not cause any other regressions.

[ghost]

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #78946 to release/7.0

/cc @tarekgh

Customer Impact

This issue is reported by the app-compat runs when running mixcore/mix.core app. The app will throw System.Reflection.AmbiguousMatchException during the configuration binding. This is a regression from the fix #78118 we had in 7.0.1 servicing. This problem occur only if the app is using a type implementing IDictionary<,> and include members with the same names as IDictionary<,> members. Like class indexer this[] or TryGetValue method. When using such class with the configuration, we use the reflection to bind to such class using the type indexer and TryGetValue method. If there is multiple members with the same name, the reflection will throw AmbiguousMatchException.

Testing

I have tested the exact code used to repro the issue with the app-compat run with referencing the packages Quartz.AspNetCore v3.3.3 and Quartz.Extensions.DependencyInjection v3.3.3 which causing the problem. I have run all our tests against the fix which is covering all cases we fixed before to ensure no other regressions. Also, I have added extra test to catch the issue we are fixing here.

Risk

Medium, touching configuration code comes with some risk but I tried my best testing the change to ensure will not cause any other regressions.

Author:	tarekgh
Assignees:	-
Labels:	area-Extensions-Configuration
Milestone:	-

[carlossanlop]

It's missing the OOB package authoring changes. I'll add them.

[tarekgh]

Thanks @carlossanlop for adding OOB authoring change.

[tarekgh]

This is approved offline by the email.

[carlossanlop]

runtime-staging not required, and passed in the previous run.
The only CI failure is known and unrelated #78778