Add 'break' into GDBRemoteClientBase::SendContinuePacketAndWaitForResponse to fix a warning

[kubamracek]

Summary

Currently, clang complains here about an non-annotated fall-through.

[labath]

looks good. plus, it seems to be a no-op, as the following case block immediately breaks.

[labath]

Looks like somebody already committed a patch like this.

source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp

for (;;) {
     PacketResult read_result = ReadPacket(response, kInterruptTimeout, false);
     switch (read_result) {
     case PacketResult::ErrorReplyTimeout: {
       std::lock_guard<std::mutex> lock(m_mutex);
       if (m_async_count == 0)
         continue;
       if (steady_clock::now() >= m_interrupt_time + kInterruptTimeout)
         return eStateInvalid;
+      break;
     }
     case PacketResult::Success:
       break;
     default:
       if (log)
         log->Printf("GDBRemoteClientBase::%s () ReadPacket(...) => false",
                     __FUNCTION__);
       return eStateInvalid;