Fixes two related URI-resolution bugs in NodeResolver. They are shipped together because both live in resolve_uri() and the regression tests for each must not regress the other (the homepage-in-subdirectory case is on #3042's don't-regress list).

#3042 — typed idType: URI fields over-resolve partial/wrong-hierarchy URIs

Typed idType: URI fields (page, post, contentNode, and the per-post-type single fields) pre-seed the target post_type into the query vars before running WP_Query. When the requested path does not match a rewrite rule, parse_request() flags a 404, but the pre-seeded post_type turns the request into an unbounded query, so WP_Query returns an arbitrary post. nodeByUri, which passes no extra query vars, correctly returns null for the same path.

The 404 guard in resolve_uri() was gated on empty( $extra_query_vars ), so it only ran for nodeByUri and never for typed fields. The guard is refined to bail on a 404 unless the request is an explicit slug lookup (idType: SLUG), which passes a name and intentionally resolves by post_name without requiring the full path to match a rewrite rule.

Result: page(id: "/child/", idType: URI) now returns null for a partial or wrong-hierarchy path (matching nodeByUri), while the correct full path still resolves, including same-slug-different-parent pages.

#3775 — homepage returns null via its full URL in subdirectory installs

When WordPress is installed in a subdirectory, the full home URL (e.g. /blog/) resolved to null. Only a literal / was treated as the home page; for the full home URL, parse_request() strips the home path and leaves an empty request that resolve_uri() did not recognize as the home page.

The home page is now detected from the parsed request (an empty $wp->request with no node- or archive-identifying query var) in addition to the literal /, so the full home URL resolves regardless of the subdirectory name. The detection only applies when permalink parsing ran, so plain-permalink installs keep relying on the literal / check.

Tests

• PageByUriTest::testTypedUriFieldIsConsistentWithNodeByUriForHierarchy asserts typed idType: URI and nodeByUri resolve a hierarchical page consistently: a partial/wrong-hierarchy URI returns null for both, and a same-slug-different-parent URI resolves the correct node. Fails before the Querying Page by URI doest require correct URI field  #3042 fix.
• NodeByUriTest::testHomePageResolvesByFullUrlInSubdirectoryInstall simulates several subdirectory names (blog, wp-in-subdirectory, and a nested cms/site) and asserts the full home URL resolves the front page while a real page below the home still resolves normally. Fails before the Getting a page by url fails when the page is the homepage, and worpress is installed inside a folder #3775 fix.

Both fixes were verified to leave the existing NodeByUriTest, PageByUriTest, and NodeBySlugTest suites green, and the don't-regress cases (#3582 percent-encoding, #2191 date archives) continue to pass. PHPCS and PHPStan (level 8) are clean.

Closes #3042
Closes #3775