Proposal: Implement TTL for UpdateAsync and TryUpdateAsync in INatsKVStore

[edison-harada]

Proposed change

I recently notice that only some methods in INatsKVStore implements the TTL like CreateAsync and TryCreateAsync.
But if the value is updated we can't provide any TTL, so the key will use the bucket TTL.

Could the "Nats-TTL" header also be implemented for the update methods?

Use case

In some scenarios we need to update values from KV Store, but when we update it the TTL is completely removed as the new version doesn't have it.
So we need to delete and recreate the item which can cause some issues during this process to avoid the update without TTL

Contribution

Yes, it should be fine :)

[mtmk]

Thanks for the proposal @edison-harada unfortunately we can't implement this. the API intentionally restricts updates since TTL behavior isn't defined in all cases i.e. when history is > 1. Of course, you can implement this in your application as an extension but we won't be supporting it in this library.
cc @ripienaar