Message details are not kept, when replacing event type

[nikku]

Describe the bug

Via #4523 we allowed replacing of typed events with their start*, intermediate* and end* variants. The purpose was two simplify our users lives. Testing the solution I found that we did not go the full length to support our users: If I have a message already configured, I'd expect that message to stay as I replace from message catch (with message A) to message start (with message A):

Steps to reproduce

1. Model message start, attach a message
2. Replace with message catch
3. See no message is attached anymore

(Same can be reproduced in different directions of replacement).

Expected behavior

• Replacing between catch* versions should keep configured details, where still valid (i.e. correlation key not supported for message start)
• Replace between throw* versions should keep configured details

Environment

• OS: Linux (Ubuntu)
• Camunda Modeler Version: v5.33.0-rc.1
• Execution Platform: any
• Installed plug-ins: None

Additional context

Found in the context of #4825.

[barmac]

This is a bummer. I did not expect this to happen when implementing the bpmn-js part :/

[philippfromme]

This also applies to signal references.

[nikku]

@philippfromme Already captured this in the expected behavior: