Optimize capturing lambdas in DependencyContextExtensions and DependencyContextJsonReader

[karakasa]

close #87911

I am kind of uncertain where to put the helper methods, as I don't want to pollute other namespaces but the methods' function are very generic and might be useful to others.

[ghost]

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

Issue Details

---

close #87911

Author:	karakasa
Assignees:	-
Labels:	area-DependencyModel, community-contribution
Milestone:	-

[ericstj]

It looks to me like the issue this issue attempts to address has an open question about the scenario being measured that notices/cares about the performance here. @Youssef1313 can you chime in on that? @ViktorHofer -- looks like you marked the original issue help-wanted can you have a look at this?

[Youssef1313]

@ericstj I don't have much info other than seeing these allocations at the startup of an Uno Platform Skia application. From the trace screenshots posted in the issue, it seems like all Uno does is this:

https://github.com/unoplatform/uno/blob/8b88124a5ebdc61a782326d96ff32e5cba5d452a/src/Uno.UI.Runtime.Skia.Gtk/Rendering/OpenGLESRenderSurface.cs#L29-L32

Then Silk.NET calls into this code and then we see these allocations.

[ViktorHofer]

I'm also surprised that this code is executed on the hot path. Nevertheless, the optimization looks trivial (replacing the lamda with a loop) so I'm OK with that. As the extension helper file is only used in a single place, it makes sense to put it next to where it is used (in DependencyModel).

[ericstj]

Here's the place in Silk.NET that's using this: https://github.com/dotnet/Silk.NET/blob/d4d55347bb5d4aa9f316b516abf05ed4d8a66bfe/src/Core/Silk.NET.Core/Loader/DefaultPathResolver.cs#L212

Probably better to use https://learn.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblydependencyresolver.resolveunmanageddlltopath?view=net-7.0