chore: add onOpenDialog api to support dialog jump

[yeze322]

Description

closes #3942

Previously, we use navTo() to support both breadcrumb jump and BeginDialog jump. It has several problems

1. Updating navTo api broke the dialog jump behavior, we fixed this bug.
2. The navTo() API belongs to ApplicationContextApi while Flow Editor prefers to consume DialogEditingContextApi. Using navTo breaks the context boundary.

For providing a more descriptive interface, this PR implements the new api onOpenDialog used only in the dialog jump scenario. In the future, we can freely update the navTo() api without bothering breaking the dialog jump behavior.

Task Item

Screenshots

[boydc2014]

This looks reasonable to me for creating a dedicated api in this BeginDialog jump.

My question is should we just update the logic to use this new API, so that we will know how much changes is needed or what the impact is. That will help us to determine whether take this or not, right?

[yeze322]

@boydc2014 The new API is consumed in useEditorEventApi.tsx where handles the click event on dialog link. That's the only usage for now, it seems not noticeable.

[boydc2014]

@boydc2014 The new API is consumed in useEditorEventApi.tsx where handles the click event on dialog link. That's the only usage for now, it seems not noticeable.

Oh, get it

[cwhitten]

@yeze322 can you address conflicts

[coveralls]

Coverage decreased (-0.002%) to 55.399% when pulling daff3b9 on yeze322:refactor/openDialog into 6ad4945 on microsoft:main.

[cwhitten]

@yeze322 still have conflicts