TabContainer active tab can become out of sync with the router state

[haynesjm42]

When changing the active tab via setActiveTabId (such as with TabSwitcher), the active tab is set before attempting to navigate via the router. It is possible that the route change would be rejected (via middleware or a canDeactivate handler) and in that case the currently rendered tab is out of sync with the router state. When using routing, the TabContainer active tab should probably only be set via router state changes to ensure they remain in sync.