fix: image fields (and other connection fields) not properly resolving when queried asPreview

[jasonbahl]

What does this implement/fix? Explain your changes.

This fixes a bug where Image fields (and other fields that return Connections) were not properly resolving when querying a page asPreview: true.

In order to support preview resolution, all field names and keys are tracked and then during resolution filters are applied to ensure the meta is resolved properly for each field (either the published post or the preview post).

Fields that return Connection types were not properly being tracked in this registry, leading to the preview resolver filter not being applied for these fields, so they would return preview data from the published node instead of the preview node.

Does this close any currently open issues?

closes #187

• failing test: https://github.com/wp-graphql/wpgraphql-acf/actions/runs/8289473478/job/22685959826?pr=189#step:7:1302
• passing test: https://github.com/wp-graphql/wpgraphql-acf/actions/runs/8289515745/job/22686073925?pr=189#step:7:1339

Any other comments?

I published a page with the following image uploaded for the image fields:

• http://uri-debugging.local/wp-content/uploads/2024/03/1920x1080.png

When I query the page with asPreview: false I see the image returned as expected:

When I query the page as an authenticated user with asPreview: true, I see the published image value (expected, since I have not made any un-published changes yet):

Now, if I go replace the image:

• published: http://uri-debugging.local/wp-content/uploads/2024/03/1920x1080.png
• preview: http://uri-debugging.local/wp-content/uploads/2024/03/andrea-de-santis-kq3hRVDiYYY-unsplash-scaled.jpg

And query asPreview: true again:

BEFORE

I still see the published image, not the preview image. 😭

AFTER

I see the image that was added to the preview but not yet published! 🥳

[coveralls]

Pull Request Test Coverage Report for Build 046b302be979fdbff9d14a546b3ee38b1f51ab2b-PR-189

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 7 of 7 (100.0%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.3%) to 63.714%

---

Files with Coverage Reduction	New Missed Lines	%
src/FieldConfig.php	1	91.84%

Totals
Change from base Build ece620b9f911b507d9cc9754d75449bf2879bc0e:	0.3%
Covered Lines:	2093
Relevant Lines:	3285

---

💛 - Coveralls