[Bug]: Request streams get disposed and there is no option to avoid it

[MikhailIvanou]

Describe the bug 🐞

Hi everyone, the problem is:

A HttpRequestMessage gets disposed after each usage of a refit client, that causes all disposable request content items get disposed as well (like streams). In my case it is not desirable behaviour, i would like to keep my streams open for some longer time.

As far as I can see, there is no option to disable this behaviour

Step to reproduce

1. Provided that we have a interface like that

public interface IAwesomeHttpClient
{
[Multipart]
[Post("/Test/Test1")]
Task<Stream> Method1(StreamPart file, CancellationToken cancellation);
[Multipart]
[Post("/Test/Test2")]
Task<Stream> Method2(StreamPart file, CancellationToken cancellation);
}

2. Then i gonna use it like that (it is pseudocode)

Stream str = await _azureBlob.OpenReadAsync();
var respStr1 = await _awesomeHttpClient.Method1(new StreamPart(str));
str.Position = 0;
// FAILED!, because 'str' has already been disposed
var respStr12= await _awesomeHttpClient.Method2(new StreamPart(str));

Reproduction repository

https://github.com/reactiveui/refit/blob/867efbdcff936b0f217889f87f684bc01df3bd1d/Refit/RequestBuilderImplementation.cs#L410C21-L410C23

Expected behavior

It would be nice to add a flag (to RefitSettings or an attrybute) determining whether HttpRequestMessage gonna be disposed.

Screenshots 🖼️

No response

IDE

No response

Operating system

No response

Version

No response

Device

No response

Refit Version

7.0.0

Additional information ℹ️

No response