fix: use start_as_current_span to maintain tracing operation chain

[girishc13]

Goals:

• resolves bug: worker runtime request handler span appears out of order #5386
• the python SDK for whatever reason doesn't consider the span started from the origin request context as the direct child span. This causes inconsistency when the trace is viewed.

Before:

After:

[codecov]

Codecov Report

Merging #5391 (66fd738) into master (f738d34) will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5391      +/-   ##
==========================================
+ Coverage   86.84%   86.91%   +0.07%     
==========================================
  Files         101       99       -2     
  Lines        6611     6565      -46     
==========================================
- Hits         5741     5706      -35     
+ Misses        870      859      -11     

Flag	Coverage Δ
jina	86.91% <ø> (+0.07%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...rate/deployments/config/k8slib/kubernetes_tools.py	73.80% <0.00%> (-26.20%)	⬇️
...deployments/config/k8slib/kubernetes_deployment.py	47.36% <0.00%> (-10.53%)	⬇️
...a/orchestrate/deployments/config/docker_compose.py	97.05% <0.00%> (-1.97%)	⬇️
jina/orchestrate/deployments/config/helper.py	92.98% <0.00%> (-1.76%)	⬇️
jina/orchestrate/deployments/config/k8s.py	99.38% <0.00%> (-0.62%)	⬇️
jina/resources/health_check/gateway.py
jina/resources/health_check/pod.py
jina/serve/runtimes/gateway/websocket/gateway.py	100.00% <0.00%> (+1.78%)	⬆️
jina/jaml/parsers/executor/legacy.py	90.00% <0.00%> (+2.00%)	⬆️
jina/clients/request/helper.py	95.74% <0.00%> (+6.38%)	⬆️
... and 1 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.