ozone/wayland: Print format that chrome used which doesn't support scanout

We got some reports that include log where we could see that
chrome used a format which doesn't support scanout. However, it's
unclear what exactly happens. Thus, this patch adds additional
information that will include the buffer format the chrome tries
to use.

Bug: 1128997
Change-Id: I09774bd506d624d4db05acc92c6a20884b664e72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424198
Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Auto-Submit: Maksim Sisov (GMT+3) <msisov@igalia.com>
Reviewed-by: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809748}

gpu/command_buffer/service/shared_image_backing_gl_texture.cc

@@ -424,7 +424,9 @@ SharedImageBackingFactoryGLTexture::CreateSharedImageInternal(
   const bool use_buffer = usage & SHARED_IMAGE_USAGE_SCANOUT;
 #endif
   if (use_buffer && !format_info.allow_scanout) {
-    LOG(ERROR) << "CreateSharedImage: SCANOUT shared images unavailable";
+    LOG(ERROR) << "CreateSharedImage: SCANOUT shared images unavailable. "
+                  "Buffer format= "
+               << gfx::BufferFormatToString(format_info.buffer_format);
     return nullptr;
   }