What does this implement/fix? Explain your changes.

This PR backfills NodeByUriTest to cover both untested cases coded for in NodeResolver::resolve_uri(), as well as additional edge cases.

Failing edge cases are marked incomplete.

What's included

• Cleaned up existing tests; added comments to indicate exactly what $query_vars are being tested for each query; and fixed/expanded testing with/without pretty permalinks.
• Test user archives
• Test post format archives
• Test date archives
• Test attachment URIs
• Test non-existent URIs
• Test posts/pages with a fixed pretty permalink prefix(Querying non-existent single page by URI returns error instead of null #1639)
• Test URIs with #anchors (URI inputs should sanitize anchor links from uris #1712 )
• Test post URIs with subpages
• Test slug conflicts across post types.
• Test updated URIs.
• Test hierarchical terms.
• Test slug conflicts across Post types and Taxonomy terms.
• Test default term URIs.
• Test CPTs and Taxonomies with base URIs.
• Test URI with add_rewrite_rule().

What's not included

• Comment URIs. Although a comments have a URI, its currently not supported by by WPGraphQL.
• Using add_rewrite_tag() and add_permastruct(). I'm not familiar enough with these methods to write a test.

Issues uncovered

The following test cases fail (as of WPGraphQL v1.13.7)

• User archives without pretty permalinks
• Post format archives (Post Format archives don't resolve with nodeByUri query #2190)
• Date archives (Date Archives don't resolve with nodeByUri queries #2191)
• Attachment URIs without pretty-permalinks
• Attachment URIs that have a post-parent (NodeByUri not resolving properly for media items #2178)
• Page and CPT with the same slug.
• Child terms with hierarchical URIs

These tests have been marked incomplete.

Does this close any currently open issues?

Part of #2366

Any relevant logs, error output, GraphiQL screenshots, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Any other comments?

• This PR intentionally doesn't attempt to fix any issues with NodeResolver::resolve_uri(), to allow for easy merging and smaller changesets on future PRs.
• If there are any other edge cases we should check for please let me know in the comments.
• It's going to take some effort to close all the incomplete tests. While I know there's no precedent for having incomplete tests in this repo, I think we should merge anyway to prevent regressions from other PRs while we work our way through 🎯 Tracking: Resolving nodes by URI #2366.

Where has this been tested?

Operating System: Ubuntu 20.04 (wsl2 + devilbox + PHP 8.0.19)

WordPress Version: 6.1.1