[DEFECT] Null Binary fields are overpopulating the logs with WARNs on page load.

Problem Statement

When a content type has a Binary Field that isnt required, when a page loads containing content of said content type, the logs get several WARN lines written to it.

Steps to Reproduce

https://github.com/user-attachments/assets/6bf266fc-b2d5-4ddf-bfd3-c58eb2d5e74d

In an environment running demo data

1. Go to Content Types
2. Open Activity Content Type
3. Add Binary field.
4. Give it a name leave the rest as default.
5. Open a new tab.
6. Go to the Maintenance Portlet.
7. Go to Log Files tab.
8. Select dotcms.log to tail the log.
9. Go back to main tab.
10. Go to the Browser Portlet
11. Open the main index page.
12. Go back to logs tab to view WARNs

Acceptance Criteria

I think a configuration property that can be set to hide these warnings might be best, or a better way of handling the repeat warnings.

dotCMS Version

23.01
Current Evergreen 26.01.02-01

Severity

High - Major functionality broken

Links

https://helpdesk.dotcms.com/a/tickets/34967

Reproduce the issue using the Content Types, Maintenance Portlet, Log Files, and Browser Portlet steps in the report, with an optional null Binary field on Activity Content Type. Start by locating the source of the repeated WARNs during page loading. Done means optional null Binary fields no longer overpopulate the logs while relevant warnings remain visible.