Support <drupal-entity> embeds in processed_text fields for Orejime consent placeholders

Problem/Motivation

orejime_media currently handles direct iframe-based embeds well, but embedded entity markup (for example ) inside processed_text fields is not consistently processed into Orejime placeholders. As a result, consent handling can be skipped for media rendered through Drupal embed workflows in text fields.

Steps to reproduce

• Enable orejime_media and configure a service/consent mapping (for example Power BI).
• Use a text format with processed_text output and embed support.
• Insert embedded entity markup (for example <drupal-entity ...> that renders external media) in a text field.
• View the rendered content on a non-admin page.
• Observe that the media may render without being wrapped by the Orejime placeholder/consent flow.

Proposed resolution

Add support for detecting Drupal embed markup in processed_text fields and ensure Orejime replacement runs at post-render stage, after text filters/rendering are applied. Only attach Orejime assets when relevant embed markup is present and at least potentially mappable to a configured consent service.

Remaining tasks

• Add/adjust logic to detect <drupal-entity> (and related embed output) in processed text preprocessing.
• Ensure post-render replacement handles resulting iframe output consistently.