Consistent error state styling and behavior for "aem-content" fields in Universal Editor

[#1]

Request for Feature Enhancement (RFE) Summary:	Implement consistent error state styling and behavior for "aem-content" fields in Universal Editor, following the example of "text" fields
Use-case:	Required "aem-content" field validation in Universal Editor
Current/Experienced Behavior:	"aem-content" fields lack a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute.
Improved/Expected Behavior:	"aem-content" fields have a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS v2025.8.21994.20250818T175115Z-250700 Universal Editor Service v20250828133131
Customer-name/Organization name:	AVIS BUDGET CAR RENTAL LLC
Screenshot (if applicable):
Code package (if applicable):

[#2]

@StanislavZh Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-35876. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.