refactor(berita): allow longer titles and descriptions ## Changes Berita authors currently cannot save titles longer than 60 characters or descriptions longer than 255 characters. Allow titles up to 300 characters and descriptions up to 50,000 characters in both creation and metadata editing. Keep the client controls, counters, and server validation consistent through shared Berita limits. Long descriptions scroll within the form. Keep Aipah Berita search previews short and include complete long descriptions in its existing paged reader, so longer news does not create oversized tool responses. Google documents no fixed maximum for [page titles](https://developers.google.com/search/docs/appearance/title-link) or [meta descriptions](https://developers.google.com/search/docs/appearance/snippet). Both can be truncated in search results according to device width. The 300/50,000 limits are SAPADA editorial choices, not Google requirements. Closes #1822. ## Release impact Patch. This extends the existing Berita authoring workflow and keeps its readers compatible with longer descriptions. It introduces no distinct application capability. ## Migration notes No database migration is required; Berita titles and descriptions already use PostgreSQL text columns. Public API consumers can receive longer complete descriptions. Aipah Berita metadata uses 255-character previews, with complete long descriptions available through the existing 24,000-character text parts. ## Validation - Passed UI policy syntax checks against base `d1d0f42ca563b4f38c98a553a227e08bcfdad39e`. - Passed React Doctor changed audit against the same base with 0 errors, 0 warnings, and complete checks. Used an ignored local temporary directory because the system `/tmp` quota was exhausted. - Passed ESLint on all changed TypeScript sources, Prettier checks on the changed form/schema/documentation files, and `git diff --check`. - Added regression fixtures for long-description paging, search previews, publication filtering, Unicode boundaries, and existing reader compatibility. Fixtures were not executed. Build, test, and dev commands were not run, as requested.