fix(gatsby): single page node manifest accuracy

[TylerBarnes]

This PR makes 2 improvements to the createNodeManifest action:

• The tests are updated to make sure each test expects the correct foundPageBy property (the way the page was found for the manifest)
• When there's only 1 related page to a node we were incorrectly storing foundPageBy as queryTracking even if was actually found via ownerNodeId or the filesystem route API

[TylerBarnes]

@KyleAMathews this is why your demo was showing the warnings when you were trying to use ownerNodeId and the filesystem route API. I think your test site only had a single related page for each node manifest 😅

[KyleAMathews]

Haha it was too simple!

…

On Fri, Oct 22, 2021, 4:45 PM Tyler Barnes ***@***.***> wrote: @KyleAMathews <https://github.com/KyleAMathews> this is why your demo was showing the warnings when you were trying to use ownerNodeId and the filesystem route API. I think your test site only had a single related page for each node manifest 😅 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33642 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAARLB3OYM6FITDB7LELQQTUIHZR7ANCNFSM5GRSLKKA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.