no matter what happens, rpc client must propagate the exception upwards. otherwise connection loop will stay blissfully unaware. CE will get stuck on the first encountered coroutine
(cherry picked from commit ac1800e8e5e8caf186e8eb90e80522eb2c6cc7bf)
IJ-CR-181068
GitOrigin-RevId: db716e4b38e3974826d9d27cddd8c23490bc91de