Resolve mismatch between `withoutActuallyEscaping` documentation and function signature

The documentation for withoutActuallyEscaping says: The escapable copy of closure passed to body is only valid during the call to withoutActuallyEscaping(_:do:). It is undefined behavior for the escapable closure to be stored, referenced, or executed after the function returns. I was surprised to see that the signature is not marked @unsafe. I didn't do the digging myself, but ChatGPT says that this was mentioned explicitly and that the rationale is that it is dynamically detected if the clo...