Filter out merge checks where no message exists
What does this MR do and why?
Currently before this change if a new merge check got introduced on the backend before the frontend adds in the new message we would show an empty merge check. This just adds an extra guard to save this from happening in the future.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.