[v5] Nested navigation within TabBar and two initial screens navigating the same destination screen

Hi

I have TabStack and the SharedElementStack.

I want to trigger the same navigation from two different screen from the tab stack.

The first screen works great. However, as soon as I trigger the navigation from the second screen, the navigation breaks when going back, the sharedElements function is not called anymore.

Below a snack reproducing my implementation and the issue I'm facing:

[snack demo](https://snack.expo.io/@sbkl/sharedelement-bug-demo)

Is it something I'm doing wrong or just because it is a prerelease for the v3 and will be fixed later on? Does that work using the latest version of this package with react navigation v4?

Thanks.

Start with the linked Snack demo and reproduce navigation to the same destination from both screens in the TabStack, then navigate back. Compare the two flows and verify whether the sharedElements function is called; done means the second-screen flow returns correctly with shared-element behavior restored.

Written by the indexing model from the issue text.