fix(core): Fix undefined type issue with nested fragment spreads

[jhmen]

Description

This pull request addresses a bug where GraphQL types in the TypeTree were becoming undefined when using nested fragment spreads. The issue stemmed from the way fragment children were being merged within the getTypeNodeByPath function. It was performing a shallow merge, failing to properly incorporate type information from nested fragments. Relates to #3337.

Checklist

📌 Always:

• [x ] I have set a clear title
• [ x] My PR is small and contains a single feature
• [x ] I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Feb 12, 2025 6:08am

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[jhmen]

I have read the CLA Document and I hereby sign the CLA

[michaelbromley]

This is very good, thanks for the fix! Please just target the master branch (since this is just a bug fix) and then we can get this merged 👍

[jhmen]

This is very good, thanks for the fix! Please just target the master branch (since this is just a bug fix) and then we can get this merged 👍

Thank you. I changed the target to master 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud