fix: graphQL bindings issue resolved (#32760)

[sneha122]

This PR resolved issue with graphQL, where if we create a graphQL with a binding and run such query, it returns with error response saying the query execution has timed out. A user had raised this issue here.

The issue was not at all reproducible on local, but It was continuously erroring out on production, release and even DPs. From the logs, we can see that issue was with GraphQLDataTypeUtils.java class. This class was somehow not getting initialised. This was due to recent changes made in PR, where the version for package was updated to v2.17.0, on local it was compiling properly but on release, production and other builds, it still seems to be referencing to the older version of it, we do not know the reason of it right now, we should further investigate this. But since this was a critical issue and we need to get user unblocked, we are going ahead with an alternate fix where we have moved the initialisation of objectMapper to serialisationUtils.java file.

1. Drag and drop a text widget on canvas, change text value to US
2. Create a new graphQL query with url as https://countries.trevorblades.com/
3. Add following in the query body and execute the API

{
  country(code: {{Text1.text}}) {
    name
	}
}

Fixes #32748
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid.

/ok-to-test tags="@tag.All"

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run:
https://github.com/appsmithorg/appsmith/actions/runs/8735651316
Commit: a03f29f
Cypress dashboard url: Click here!

• Refactor
• Updated serialization configuration across various data types and plugins to enhance functionality and compatibility using a centralized utility method.
• New Features
• Introduced a new method to standardize object mapper configurations, improving serialization processes across the application.

---

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No