JIT: Double check `lvHasExplicitInit` when resuming runtime async functions

[jakobbotsch]

Explicit init is computed during SSA which is before runtime async runs. We may forego zeroing that ends up being necessary if GC happens during runtime async resumption.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[jakobbotsch]

We introduce TLS access as part of the IR inserted to save contexts, and that means there will always be a GC safe point between the entry and the user's code. So I don't think there is a problem here in practice.

I still think an explicit check is warranted in optRemoveRedundantZeroInits, but it can be done in .NET 12.

[jakobbotsch]

Nope, I was able to produce an example repro that reports a garbage reference to the runtime using async versions. Moving it back...