Fix the case when a coroutine is dynamically replaceable when targeting older os
In such a case there will be a call to swift_getFunctionReplacement50 in
the entry block, followed by a call to the replacement function before
the coro.begin. We can safely ignore the call to the replaced function even
though it uses function arguments.