Updating screenshots to remove outdated OC constructs

[StevePascoe]

Description

When should this change go live?

• [ ] This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• [x] This is already available but undocumented and should be released within a week. (add available & undocumented label)
• [ ] This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• [ ] This is part of a scheduled alpha or minor. (add alpha or minor label)
• [ ] There is no urgency with this change (add low prio label)

PR Checklist

• [ ] The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• [ ] My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• [ ] My changes are for an already released minor and are in a /versioned_docs directory.

• [ ] I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • [x] Engineering team review
  • [x] Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[mesellings]

@giorgionaps can you please support @StevePascoe with a TW review?