Navigating with nested routes to another tab in AutoTabsScaffold

[tyler401go]

I'm not sure if this is expected behavior (I have dug quite a bit into the documentation but haven't found clarity). Using an AutoTabsScaffold setup, If navigating to a nested page that is on a different tab from the current one it will not push parent routes, even if explicitly given in the .navigate() call.

Here is a minimum reproducible app showcasing the behavior. I would expect that when tapping the button on the FirstTabPage that both the ThirdTabRoute and NestedRoute will get pushed onto the third tab stack, so the AutoLeadingButton would be available. However, it is only available if going through the ThirdTabPage

https://github.com/tyler401go/auto_route_issue

@Milad-Akarie This could very well be me not understanding navigate and how it interacts with children, but any help or insight would be greatly appreciated. Thanks for the great library.