fix(graphql): graphql instrumentation throw for sync calls

[blumamir]

Which problem is this PR solving?

• fixes @opentelemetry/instrumentation-graphql Error when running synchronously #1082

The issue is that graphql resolvers can either be a promise or a sync function. Instrumentation wrapped each result with a promise (using asyncSafeExecuteInTheMiddle) which was confusing graphql, making it fail for sync runs, and changing the span times in a way that doesn't make sense (sync calls now overlapped).

Short description of the changes

• When wrapping graphql resolver, check if the result is a promise and handle promise and sync response accordingly.

I added test and run test-all-versions on the PR

[codecov]

Codecov Report

Merging #1254 (1b2d308) into main (180b336) will decrease coverage by 2.29%.
The diff coverage is 86.20%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1254      +/-   ##
==========================================
- Coverage   96.08%   93.79%   -2.30%     
==========================================
  Files          14        7       -7     
  Lines         893      467     -426     
  Branches      191       89     -102     
==========================================
- Hits          858      438     -420     
+ Misses         35       29       -6     

Impacted Files	Coverage Δ
...opentelemetry-instrumentation-graphql/src/utils.ts	92.85% <85.71%> (ø)
...try-instrumentation-graphql/src/instrumentation.ts	91.66% <100.00%> (ø)
...trumentation-document-load/src/enums/EventNames.ts
...ation-user-interaction/src/enums/AttributeNames.ts
...y-instrumentation-long-task/src/instrumentation.ts
...lugin-react-load/src/BaseOpenTelemetryComponent.ts
...entation-document-load/src/enums/AttributeNames.ts
...etry-plugin-react-load/src/enums/AttributeNames.ts
...metry-propagator-aws-xray/src/AWSXRayPropagator.ts
...etapackages/auto-instrumentations-web/src/utils.ts
... and 13 more

[obecny]

lgtm