Too many S3 requests to dataset_logo_original for dataset thumbnail

What steps does it take to reproduce the issue?

• When does this issue occur?

When trying to load a dataset thumbnail and the dataset author/admin didn't define a thumbnail.

• Which page(s) does it occurs on?

It occurs on pages that require a dataset thumbnail on load.

• What happens?

Dataverse tries to access a S3 file that doesn't exist, this creates a lot of unwanted requests to the S3 endpoint.

• To whom does it occur (all users, curators, superusers)?

All users.

• What did you expect to happen?

I have configure the feature flag disable-dataset-thumbnail-autoselect to On, but documentation isn't clear on the full effects of this setting. In dataset table there is a column usegenericthumbnail, but the Thumbnail+Widgets page for datsets doesn't have a way to enable this setting. Is this option configured by this feature flag?
I have also configured S3 following this section of the documentation, but in the same table the column storagedrive is set to null for all entries. Shouldn't this have the storage driver ID configured ?

Which version of Dataverse are you using?
6.6

Any related open or closed issues to this bug report?
No

Start by tracing dataset thumbnail loading for datasets without an author or admin thumbnail, then inspect the disable-dataset-thumbnail-autoselect feature flag and the dataset table fields usegenericthumbnail and storagedrive. Reproduce the missing S3 object lookup and verify that thumbnail loading avoids repeated requests while the flag and storage-driver behavior are clear.