The current Opal system tools for CMS (SaaS) cover creating, updating, publishing, and deleting content items (cmscreatecontentitem, cmsupdatecontentitem, cmspublishcontentitem, cmsdeletecontentitem, etc.), but there's no tool to move a content item into a review/approval state, or to approve/reject an item that's already in review. cmspublishcontent_item only covers going live — it doesn't cover the intermediate workflow step where content sits in "Ready for review" and an approver acts on it.

Why it matters: Optimizely CMS supports content approval workflows (submitting drafts for review, approving or rejecting with comments) as a core editorial feature, but that workflow currently can't be driven through Opal at all. Anyone using Opal to manage content has to leave the assistant and go into the CMS UI to submit for review or approve/reject — breaking the "manage content end-to-end via Opal" flow for any team using approval-based publishing.

Ask: Add system tools to the CMS (SaaS) Opal toolset for content review actions, for example:

cmssubmitforreview (or similar) — move a content item's draft version into a review/pending-approval state.
cmsapprovecontentitem — approve a content item in review, optionally advancing it toward publish.
cmsrejectcontent_item — reject a content item in review, optionally with a comment/reason, returning it to draft.

These should mirror the parameter pattern already used elsewhere (e.g., ContentKey, ContentVersion, optional Comment) for consistency with cmspublishcontentitem and cmsupdatecontentitem.