WYSIWYG editors are not always initialized on first load

[woutervroege]

Bug Description

WYSIWYG editors are not initialized on first load in dynamic field contexts (for example: repeater subfields, conditional groups, and fields revealed after interaction).
They only appear after saving the post and reloading the edit screen.

Impact

Editors see empty/plain areas instead of rich text editors while editing.
Field UX feels broken/inconsistent in repeaters and conditional logic.
Risk of bad content formatting because users may type into non-initialized fields.

Expected Behavior

Any visible WYSIWYG field should initialize immediately when it is rendered or becomes visible, including:

• initial page render
• newly added repeater rows
• fields/groups shown by conditional logic
• fields injected by async/dynamic rendering

Actual Behavior

Initialization seems to run only once for a subset of fields on load.
Fields created later or hidden-then-shown miss TinyMCE/Quicktags bootstrap until a full save + reload.