fix(edit-content): join category inodes for API submission

[oidacra]

Summary

• Add category-specific handling in processFieldValue() to join the array of category inodes into a comma-separated string before sending to the API
• The category component sends string[] of inodes via onChange(), but the backend expects a comma-separated string

Closes #33931

Acceptance Criteria

• Categories selected in new edit content mode are saved correctly
• Categories display correctly after saving and reopening
• No regression on other field types

Test Plan

• yarn nx test edit-content --testPathPattern=functions.util — all tests pass
• Manual: Create content with categories, save, verify categories persist

Changed Files

File	Change
libs/edit-content/src/lib/utils/functions.util.ts:615-618	Added CATEGORY handler in processFieldValue()

This PR fixes: #33931

[claude]

Claude finished @oidacra's task in 2m 47s —— View job

---

Claude finished @oidacra's task in 2m 52s —— View job

---

I'll analyze this and get back to you.

[claude]

Rollback Safety Analysis

• Read rollback-unsafe categories reference
• Get full PR diff
• Analyze diff against all unsafe categories
• Apply appropriate label

Result: Safe To Rollback -- label applied.

The diff contains only two frontend TypeScript files. All 14 rollback-unsafe categories (C-1 through M-4) were checked; none apply. No DB migrations, no ES mapping changes, no API contract changes, no data model changes. Rolling back simply reintroduces the original category-not-saving bug with no broader impact.

View job run

[Copilot]

Pull request overview

This PR addresses category fields not persisting in the New Edit Content experience by normalizing the category form value into the backend-expected submission format (comma-separated string) before calling the save/workflow API.

Changes:

• Added CATEGORY-specific handling in processFieldValue() to serialize string[] category inode arrays as a comma-separated string for API submission.