Thumbnail image selection logic change in search listing view

Problem Statement

In version 23.01, the content search listing view displayed image thumbnails based on the first populated binary/image field in a contentlet, even if it was not the first binary field sequentially defined in the content type.

This behavior appears to have changed in the latest version (evergreen).
Only the first binary field (in order of definition) is considered for rendering a thumbnail.
If this field is either:
Not populated, or
Populated with a video file (which doesn’t render as a thumbnail), Then no thumbnail is displayed, even if subsequent binary/image fields are correctly populated with valid image assets.

Steps to Reproduce

https://drive.google.com/file/d/1ZCmYEIVoFmHRoWQ4lIEgLTxV5d\_MPzPq/view?usp=sharing

Acceptance Criteria

If this is an expected change, let us explain to the customer why this was done.
If this is a bug introduced, we should consider the image or binary uploaded though it might not be the first one

dotCMS Version

23.01 Works
Noticed in evergreen

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/32120

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Start by reproducing the thumbnail behavior in the search listing view using the linked recording and compare evergreen with version 23.01. Trace how binary and image fields are selected when the first field is empty or contains a video. Done means the expected behavior is confirmed with the customer, and either the selection behavior is corrected or the change is documented.