Fix query runner exceptions not being handled properly

[Weiko]

Context

We recently introduced a try catch in the different resolvers of the query runner to handle exceptions via workspaceQueryRunnerGraphqlApiExceptionHandler and convert them to proper errors. However this was never called as expected because query runner methods were async.
This is a regression from #6324

Before

After

[greptile-apps]

PR Summary

The pull request addresses exception handling in various resolver factories by making resolver functions asynchronous and using try-catch blocks to ensure proper error handling.

• /packages/twenty-server/src/engine/api/graphql/workspace-resolver-builder/factories/create-many-resolver.factory.ts: Updated to handle exceptions with async/await and try-catch.
• /packages/twenty-server/src/engine/api/graphql/workspace-resolver-builder/factories/create-one-resolver.factory.ts: Made resolver function asynchronous and added try-catch for error handling.
• /packages/twenty-server/src/engine/api/graphql/workspace-resolver-builder/factories/delete-many-resolver.factory.ts: Ensured proper exception handling with async/await and try-catch.
• /packages/twenty-server/src/engine/api/graphql/workspace-resolver-builder/factories/delete-one-resolver.factory.ts: Updated to handle exceptions using async/await and try-catch.
• /packages/twenty-server/src/engine/api/graphql/workspace-resolver-builder/factories/find-duplicates-resolver.factory.ts: Added async/await and try-catch for proper exception handling.

_{9 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}