Add TTL versions of UpdateAsync/TryUpdateAsync to INatsKvStore

[caleblloyd]

Expose the ttl-versions of update

[mtmk]

sorry for the delay on this one @caleblloyd. i'm guessing it's for extending the ttl i.e. sliding expirations? I'm not sure if this works as expected.

btw is this same subject would you say? #831 (comment)

[caleblloyd]

Yes, for sliding window updates. I think it is working fine here, had to cast to the concrete implementation though:

https://github.com/code-cargo/NatsDistributedCache/blob/4a4e7ed84e22df9e969597ee6df226333d9f5e4d/src/NatsDistributedCache/NatsCache.cs#L349

[mtmk]

ah ok. so just to double check, is it doing what it's supposed to do? cause my understanding is that sliding expiration wasn't supported by the server

[caleblloyd]

True, I don't think sliding expiration is technically supported by the server. But it can be achieved by doing a Get, followed by an Update with Optimistic Concurrency Control on the revision that was retrieved, sending the exact same value back with a new TTL.

This PR is exposing the UpdateAsync (already exists in implementation) and TryUpdateAsync (added to the implementation) methods with TTL Paramaters in the INatsKvStore interface

They would be useful for anyone using the interface who wants to do an update with Optimistic Concurrency Control and a TTL, not just for sliding expiration.

It's more of an interface parity change than anything new... For example the TTL versions of CreateAsync and TryCreateAsync are already in the interface. While we are on the subject though, I noticed that there are not TTL versions of the PutAsync and TryPutAsync methods on the interface... Shall I add those to this PR as well?

[mtmk]

There is a suggestion against put here https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-48.md#storing-values

[mtmk]

LGTM