fix(bitswap/client/providerquerymanager): use non-timed out context for tracing

[aschmahmann]

@gammazero going to test this out, but this seems like a relatively simple fix to the issue where we cancel the context which stops the tracing. Instead we pass the uncancelled context from the parent.

Note: I skipped the changelog since it seems like a fairly minor change, but can add if you think it makes sense

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.38%. Comparing base (625aadd) to head (e11bbf9).
Report is 5 commits behind head on main.

@@           Coverage Diff           @@
##             main     #721   +/-   ##
=======================================
  Coverage   60.38%   60.38%           
=======================================
  Files         243      243           
  Lines       31021    31021           
=======================================
+ Hits        18731    18732    +1     
+ Misses      10626    10624    -2     
- Partials     1664     1665    +1     

Files with missing lines	Coverage Δ
...ernal/providerquerymanager/providerquerymanager.go	89.73% <ø> (+0.76%)	⬆️

... and 11 files with indirect coverage changes

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[gammazero]

I still see one missing item in the trace, but this is better.