Support for ASP.NET Core integration request/response model

**Describe the issue**
`OpenApiTriggerFunction` endpoints such as `RenderSwaggerDocument`, `RenderOpenApiDocument`, etc. do not currently work with isolated model and [ASP.NET Core integration](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide#aspnet-core-integration).

I think that the library should include another set of endpoints which use `HttpRequest` and `HttpResponse`/`IActionResult`.

**To Reproduce**
Steps to reproduce the behavior:
1. Start application with [Core Tools version 4.0.5240 or later](https://learn.microsoft.com/en-us/azure/azure-functions/functions-run-local)
2. Navigate to api/swagger.json
3. Blank page is displayed

**Expected behavior**
OpenAPI json document is displayed

**Screenshots**

**Environment (please complete the following information, if applicable):**
- OS: Windows
- Browser: edge
- Version [e.g. 22]: Tried both 1.5.1 and 2.0.0-preview2

**Additional context**
-

Start with the OpenApiTriggerFunction endpoints named in the issue, especially RenderSwaggerDocument and RenderOpenApiDocument, and reproduce the blank api/swagger.json response using Core Tools 4.0.5240 or later. Compare the isolated ASP.NET Core integration request/response model with the existing endpoint approach. Done means the OpenAPI JSON renders correctly through the requested HttpRequest and HttpResponse/IActionResult endpoints.

Written by the indexing model from the issue text.