currently navigation-reset only works properly if you reset to a simple route
this fix allows us to use navigation reset with more complex routes, by
ensuring that the navigation stack is populated properly so that navigate
back doesn't end up emptying the stack.
this is temporary as the proper way to do navigation in general would be
to get rid of view id and navigation-stack entirely, since it is a duplication
of the state of react-navigation
Signed-off-by: yenda <eric@status.im>
500d2cc787