fix(router): correctly deactivate children with componentless parent

[atscott]

During route activation, a componentless route will not have a context created
for it, but the logic continues to recurse so that children are still
activated. This can be seen here:

angular/packages/router/src/operators/activate_routes.ts

Lines 151 to 158 in 362f45c

	if (future.component) {
	// If we have a normal route, we need to go through an outlet.
	const context = parentContexts.getOrCreateContext(future.outlet);
	this.activateChildRoutes(futureNode, currNode, context.children);
	} else {
	// if we have a componentless route, we recurse but keep the same outlet map.
	this.activateChildRoutes(futureNode, currNode, parentContexts);
	}

The current deactivation logic does not currently account for componentless routes.

This commit adjusts the deactivation logic so that if a context cannot
be retrieved for a given route (because it is componentless), we
continue to recurse and deactivate the children using the same
parentContexts in the same way that activation does.

Fixes #20694
Fixes #40196

regular presubmit and global
additional integration tests. Compared with results from clean client and a second run from this PR, they have the same number of failures so these are likely pre-existing and/or flakes. Pending code approval, all g3 signs seem to indicate that this should be okay to merge.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}