feat(binary-field): migrate dot-edit-content-binary-field lib to Tailwind CSS / PrimeNG 21

Description

The dot-edit-content-binary-field library (and its dotcms-binary-field-builder custom element app) was rolled back from the Angular 20→21 / PrimeNG 17→21 migration commit (618fd32060) due to multiple regressions:

• NG0950 errors in JSP pages — input.required() signal inputs are incompatible with createCustomElement from @angular/elements
• Tailwind CSS was never wired into the dotcms-binary-field-builder app's build, breaking all layout
• The PrimeNG 21 Lara theme provider (provideDotCMSTheme) was missing from AppModule, leaving all PrimeNG components unstyled
• The global .pi { display: flex; width: 20px; aspect-ratio: 1/1 } rule from _misc.scss conflicted with PrimeNG 21's button flex layout, misaligning all button icons
• Multiple PrimeNG 17 styleClass button variants broken under PrimeNG 21

The rollback restored all pre-migration SCSS files and HTML templates. This task tracks the proper forward migration so the field is fully aligned with the rest of the codebase (Tailwind CSS v4 + PrimeNG 21 Lara theme).

Fixes already applied to the builder app (must be preserved during migration)

Components to migrate

All under libs/edit-content/src/lib/fields/dot-edit-content-binary-field/:

• dot-edit-content-binary-field.component (main + .scss)
• components/dot-binary-field-editor/ (HTML + .scss)
• components/dot-binary-field-preview/ (HTML + .scss)
• components/dot-binary-field-ui-message/ (HTML + .scss)
• components/dot-binary-field-url-mode/ (HTML + .scss)
• components/dot-binary-field-wrapper/

PrimeNG 17 → 21 button API reference

Acceptance Criteria

• All SCSS files deleted and replaced with Tailwind CSS utility classes in templates
• All styleClass on <p-button> replaced with PrimeNG 21 props
• @Input() setter + backing signal pattern preserved in .component.ts (NOT reverted to input.required()) to maintain @angular/elements compatibility
• Builder app fixes preserved (Tailwind setup, provideDotCMSTheme, dialog backdrop, button icon override)
• Field renders correctly in JSP pages — no NG0950, no unstyled components
• URL import dialog, editor dialog, and file preview match design spec
• Tooltip displays correctly on disabled AI button ([tooltipOptions]="{ showOnDisabled: true }")
• All unit tests pass (yarn nx test edit-content)

Additional Context

• The dotcms-binary-field-builder app exposes <dotcms-binary-field> as a custom HTML element via createCustomElement — embedded in JSP pages. This is why input.required() cannot be used.
• PrimeFlex is no longer available — Tailwind utilities only.
• Reference the migration commit 618fd32060 for the intended Tailwind output structure.
• Related rollback: branch issue-34552-tags-portlet-feedback.