[wasm] Avoid Spilling Many GC-ref Typed Tree Temps

[adamperlin]

The current fgWasmSpillRefs pass spills all outstanding GC-ref typed temporary values, even if those temps are consumed by the most immediate managed, non-helper call. However, for a managed non-helper call, it should be the callee's responsibility to maintain GC safety of any incoming GC-ref typed args (either by spilling to a pinned stack home in the prolog or potentially avoiding spilling at all, see #135543). In the R2R fixup case, where a thunk will fix up the call target on first invocation, we should also be GC-protecting all incoming args by default (See the spilling logic in crossgen2 WasmImportThunk.cs).

This PR removes the need for spilling in cases like:

MyClass x = Allocate();
Use(x);

Where Use is managed.

Note that the spilling STILL needs to happen for nested calls, where a ref has an outstanding use which is NOT its most immediate parent.

MyClass x = Allocate();
M(x, F()) // <-- temporary value of x is an operand of the call to M, and may be live across the other sub-tree call, F where a GC might occur.

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).
10 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

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