[FEATURE] PageAPI/GraphQL Style Properties Delivery

Problem

Problem
PageAPI and GraphQL responses don't include style properties, making it impossible for headless applications to render components with their configured styling. Real-time preview in the Style Editor also needs this delivery system to show accurate styling.

Goal

Goal
Enhance both PageAPI and GraphQL page query to return style properties with contentlet data, maintaining the existing response structure while adding style information. This enables both headless applications and real-time preview functionality.

Personas
Developer teams: Need style data available in headless applications
Content teams: Need accurate preview of their style changes (indirect benefit)

Target Personas

• Developer teams
• Content teams
• DevOps teams
• System administrators (dotCMS)

Demo Expectations

Demo Expectations
PageAPI/GraphQL responses include styleProperties field for each contentlet
Both APIs return identical (as possible) style data maintaining consistency
Style data properly cached to prevent performance impact
Demo shows saved style properties flowing through to page rendering

Acceptance Criteria

No response

User Stories

No response

Links

No response

No file or test paths are provided. Start by locating the PageAPI and GraphQL page-query entry points, then compare how contentlet data and style properties are currently delivered and cached. Done means both APIs expose consistent styleProperties for each contentlet without a performance regression.