rtmessage: fix resource cleanup order in rtConnection_CreateInternal

[Copilot]

Fixed cleanup order inconsistency in error paths when buffer allocations fail. The original fix destroyed synchronization primitives in a different order than the existing cleanup function.

Changes

• Reordered cleanup to match existing pattern at lines 770-773: mutex → callback_message_mutex → callback_message_cond → reconnect_mutex
• Applied consistent ordering to both send_buffer (lines 553-556) and recv_buffer (lines 564-567) allocation failure paths

// Before: condition variable destroyed after reconnect_mutex
pthread_mutex_destroy(&c->callback_message_mutex);
pthread_mutex_destroy(&c->reconnect_mutex);
pthread_cond_destroy(&c->callback_message_cond);

// After: condition variable destroyed between mutexes
pthread_mutex_destroy(&c->callback_message_mutex);
pthread_cond_destroy(&c->callback_message_cond);
pthread_mutex_destroy(&c->reconnect_mutex);

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[svc-rdkeportal01]

Thank you @Copilot for creating this auto-fix PR! However, this issue has already been addressed.

The cleanup order was fixed in commit 8165c75 (pushed at 20:32 UTC), which reordered the cleanup to match the existing pattern at lines 770-773.

Since the fix is already in PR #398, this sub-PR is no longer needed. Closing as duplicate. 🙏