Describe the bug:

When the network is throttled, the navigation embeddable edit flyout is delayed by some sort of async behaviour happening internally - even if we are waiting for something to load, this should not stop the flyout from opening. FYI the image embeddable suffers from the same thing (we don't need to fix this) - so maybe it has something to do with how we are opening the flyout in getExplicitInput (since we took inspo from the image embeddable for this)? Need to investigate

Video:

Notice that the image "pops in" for the empty state even on the second load, most likely because we are importing it in the flyout itself - as part of this, we should probably make it so that this is only loaded/imported a single time.