feat(router): Allow resolvers to read resolved data from ancestors

[atscott]

This commit updates the resolver execution to ensure that resolvers in children routes are able to read the resolved data from anything above them in the route tree. Because resolvers on one level block execution of those below, it seems more of an oversight in the initial implementation than anything else that this wasn't already possible.

resolves #47287

[atscott]

reviewer note: This has a green TGP though maybe it should still be considered a breaking change? Technically if there was static data with the same key as a resolver in a parent, reading that data in the child resolver would have given you the static value rather than the resolved value from the parent. This seems....technically possible but quite unlikely. I've marked the target as "major" out of caution for this, but maybe it doesn't need a callout in the breaking changes notes.

[kirjs]

This PR was merged into the repository by commit 7c12cb1.

The changes were merged into the following branches: main

[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.}