Fix trace context lost when squashing and rethrowing GQL errors

[myieye]

In this case the GQL error has almost certainly already been traced and we don't want to lose that info or else our global error handler will retrace it with a new trace.

[myieye]

• Fix trace context lost when squashing and rethrowing GQL errors #1191 👈
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @myieye and the rest of your teammates on Graphite

[github-actions]

UI unit Tests

12 tests  ±0   12 ✅ ±0   0s ⏱️ ±0s
 4 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit d9f87b2. ± Comparison against base commit 0a42f92.

♻️ This comment has been updated with latest results.

[hahn-kev]

when I use the sandbox GQL 500 I get this error in the console

Uncaught (in promise) Error: Object has already been traced (60abceb2db8c181adeba64eb41d328b0 vs 60abceb2db8c181adeba64eb41d328b0).
    TraceItError types.ts:27
    traceIt types.ts:33
    tryCopyTraceContext types.ts:51
    squashErrors gql-client.ts:305
    throwAnyUnexpectedErrors gql-client.ts:285
    queryStore gql-client.ts:203
    sync index.js:150
    unsubscribers index.js:164
    set index.js:56
    m queryStore.ts:185
    subscribe wonka.mjs:1068
    scan wonka.mjs:402
    switchMap wonka.mjs:591
    switchMap wonka.mjs:591
    applyInnerSource wonka.mjs:111
// ... etc