Initial implementation of per-key-TTL for KV

[stebet]

Note

• to be merged into Server 2.11 Features #733

• Adds support to set the AllowMsgTTL flag for KV streams
• Adds a Timestamp ttl optional parameter to the PutAsync<T> method on INatsKVStore
  • Note that this does break API backwards compatibility if users are using their own serializers, but that's seems to be how it's done in Go client, so it's up to you if you want to create a separate overload for each method that can accept a TTL value
• Added a single test to test the TTL functionality. This currently requires the tests to have access to the latest nightly binary

TODO:

• More exhaustive tests
• Add support to the CreateAsync/UpdateAsync API methods

see also ADR-43

[mtmk]

we're hoping to merge this into server 2.11 branch before server release #733

[jodydonetti]

Can't wait for per-key TTL, it will allow usage of NATS in FusionCache too.

Thanks for all the hard work!

[mtmk]

LGTM thanks @stebet

There are still details to be worked out e.g. around SubjectDeleteMarkerTTL but this PR introduces support for per-message/key TTL feature for new server 2.11 soon to be released. We can have follow up PRs into the server-2.11-features branch when we have more implementation details available.