Weird tracing results

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

I use gRPC service with a server streaming endpoint. And the client's span duration is much longer than the server's one while the only thing client does is reading all items from the stream.


It looks like ASP.NET Core instrumentation does not take stream lifetime into account, whereas client gRPC instrumentation does.

### Expected Behavior

I expect span to live as long as gRPC stream does.

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

_No response_

### Anything else?

_No response_