fix #626 Microsoft.Azure.Functions.Worker.Extensions.OpenApi throws System.IO.FileNotFoundException

[lgp1985]

This addresses the #626 so the behavior of Microsoft.Azure.Functions.Worker.Extensions.OpenApi matches Microsoft.Azure.WebJobs.Extensions.OpenApi.

After the change I could confirm the migrated project can safely skip attempting to load unused types.

[lgp1985]

Hey all, I would love to have this reviewed, so we have consistent behavior between both in-process and isolated workers.

[lgp1985]

I would really appreciate this to be reviewed.

[Strandfelt]

@justinyoo I see you were the latest active MS staff in here. Any chance you could look at this? This project is failing for .NET 8 projects.

[Strandfelt]

How about you @kendaleiv, can you help get this reviewed?

[davidpetric]

Unfortunately, the project's limited recent development has led to challenges, including compatibility issues with the latest Azure Functions worker/isolated packages and Asp.Net integration. This situation is particularly challenging as we rely on this project for our Serverless APIs.

Moreover, it's disappointing to observe that Microsoft is advocating for Azure Functions in Serverless API development. This underscores the importance of reassessing our current strategy, especially considering the reported difficulties in the smooth integration of various Microsoft services.