Perf: unset EnableContentResponseOnWrite dotnet#22999

[umitkavala]

I've create draft version to check implementation is correct.
See https://devblogs.microsoft.com/cosmosdb/enable-content-response-on-write/

[dnfadmin]

All CLA requirements met.

[AndriySvyryd]

Generally looking good, just add ETag tests as mentioned in #22999 (comment)

[AndriySvyryd]

Also if the option hasn't been set to any value you can check whether we'll need the content at all: jObjectProperty?.ValueGenerated == ValueGenerated.OnAddOrUpdate

[umitkavala]

Thanks @AndriySvyryd I'll have do required changes.

[umitkavala]

I've a problem with access option value
Its not good idea to cast like this.
var enableContentResponseOnWrite = ((ICosmosSingletonOptions)Client.ClientOptions).EnableContentResponseOnWrite;
And realized that CosmosClientOptions does not have property for that. So using option is not possible I guess.
Do you have any suggestion?

[AndriySvyryd]

You can now convert this to a non-draft PR to allow the tests to run

[umitkavala]

Seems we can only have 1 constructor on DBcontext. so I couldn't add new constructor but handled with CreateOptions using default constructor of ConcurrencyContext

[AndriySvyryd]

Thanks for your contribution!

[umitkavala]

wow. I'm so happy to contribute :) How can I track this change will release?
I'll continue to contribute of course!

[AndriySvyryd]

It should already be available in daily builds of 6.0.0
We'll start releasing previews next year.