Migrating azure functions to .net8 isolated, AspNetCore HttpTriggers Hang

Multiple people are reporting an issue after migrating from net6 in-process to net8 isolated. A [previous issue](https://github.com/Azure/Azure-Functions/issues/2425) was opened but closed, so I am creating a new issue here.

I believe it is related to AspNetCore. If you refactor the httpTrigger to use the built-in http model (HttpResponseData, HttpRequestData) and ConfigureFunctionsWorkerDefaults() the function works. If you enable AspNetCore ConfigureFunctionsWebApplication() and kill the built-in http model... the AspNetCore http trigger hangs/breakpoint never hit. Weird thing is, if you create a brand new isolated .NET 8 function app and enable AspNetCore + build out the same httpTrigger function, it works. I have mirrored all config, references, project settings between the new function project vs the migrated. No go. I've deleted all /obj /bin directories + clean, rebuild, restart and it does not help. At this point, I think its an environment issue - maybe something is cached w/ net6 on the machine. I'm not going to migrate to net8 if it means all devs have to reinstall VS or the like if that is the issue.