Use-After-Return detection was disabled when AddressSanitizer was initially stood up because various components in CoreCLR (and possibly NativeAOT) check if a pointer is on the current thread's stack, which doesn't work with the fake stacks that the Use-After-Return detection uses to implement the feature. AddressSanitizer has APIs in its "public interface" that we can use to detect if a pointer is in the current thread's fake stack. We should use this feature in the places where we are asserting that a particular pointer points to the thread's stack and enable the detection.