Duplicating a Sequencer causes events from the original sequence to fire when the second Sequencer is ran

When using a Sequence that is a duplicate of another, without changing the event names, the duplicate Sequence will still fire off the event from the original even if the values are changed. Changing the event name causes the following warning to display and the event not to fire.

LogMovieScene: Warning: Failed to trigger the event 'E2' because the function does not exist on director instance.

This issue was reported and tested in 4.21 (CL-4541578). This was reproduced in Main 4.22 (CL-4560050). The Sequencer Event workflow has changed since 4.20.3 (CL-4369336).

1. Open the UE4 Editor and create a Blank Template project
2. Create a level sequence called SEQ1
3. Add an event track and an event called "E1", and call a print string on this event to play in editor that says "E1" in red.Click the "Call in Editor" checkbox then save and compile the sequencer director. Now when you scrub over this event "E1" in red should print on screen.
4. In the content browser copy and paste SEQ1 and it should auto name to SEQ2. Open SEQ2.
5. Open the "E1" event on SEQ2 and change just the print string name to "E2" and make it blue.
6. Scrub over the timeline "E1" event on SEQ2 and "E1" prints in red instead of "E2" in blue as expected.

Results: SEQ2 E1 event is fired on SEQ1 E1 event even though it should only fire on itself.

Expected: SEQ2 E1 event should only fire itself and not an event on a different sequence director regardless of both event names being "E1".

Bug UE-66454 Isnt scheduled to be fixed until 4.22 and this is a big problem!