OSR method may require kept-alive this in cases where base method didn't

[AndyAyersMS]

A couple examples in the OSR stress weekend experimental runs.

Because of inlining the reporting of this for generic contexts is needed in an OSR method, but not in the base method. This violates an assumption that both methods would agree on this aspect.

runtime/src/coreclr/jit/lclvars.cpp

Lines 6193 to 6204 in ca7f199

	// OSR methods use the original method slot for the cached kept alive this,
	// so don't need to allocate a slot on the new frame.
	if (opts.IsOSR())
	{
	if (lvaKeepAliveAndReportThis())
	{
	PatchpointInfo* ppInfo = info.compPatchpointInfo;
	assert(ppInfo->HasKeptAliveThis());
	int originalOffset = ppInfo->KeptAliveThisOffset();
	lvaCachedGenericContextArgOffs = originalFrameStkOffs + originalOffset;
	}
	}

Should not be too hard to report the kept-alive this in the OSR method on it's part of the frame. Looks like CodeGen::genReportGenericContextArg might just work for OSR frames, though that needs to be verified.

category:correctness
theme:osr
skill-level:intermediate
cost:small
impact:small

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[AndyAyersMS]

Fixed by #51057.