Handles the instrumentation case where a future is only used to wait_for

[chrisguidry]

In our OpenTelemetry instrumentation, we were assuming that if we were
resolving a future before running a task, it must be a parameter. This
isn't true in the case where a future is used in wait_for, where the
context's parameter_name won't be set.

Fixes #16708

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

[codspeed-hq]

CodSpeed Performance Report

Merging #16709 will not alter performance

_{Comparing no-parameter-name (3574228) with main (f9f3b7b)}

Summary

✅ 2 untouched benchmarks