Support an @Expiry, @Expiration or @TTL annotation

[aaronjwhiteside]

Just like we have @Field @Id and @Version support, it would be good to have a field to read the document expiry value from.

This field should support being of the type int, long, Duration and some subset of classes from java.time.*.

[aaronjwhiteside]

Being able to annotate a field to nominate it as containing the expiry value would also allow programmatic control of expiry when using a Repository.

User user = new User();
user.setExpiry(Duration.ofHours(1));
userRepository.save(user);

Analogous to:

template.insertById(User.class)
   .withExpiry(Duration.ofHours(1))
   .one(user);

[mikereiche]

Should be supported with #1149 in org.springframework.data:spring-data-couchbase:4.3.0-M2 by:

public interface UserRepository extends CouchbaseRepository<User, String>, DynamicProxyable<UserRepository> {...}

userRepository.withOptions(InsertOptions.insertOptions().expiry(Duration.ofHours(1)).save(user);

[aaronjwhiteside]

userRepository.withOptions(InsertOptions.insertOptions().expiry(Duration.ofHours(1)).save(user);

So if the entity already has a field annotated with @Expiration, what is the purpose of specifying the expiry via options? Shouldn't we just read the value of the field? There is a lack of symmetry here...

Then there is also the issue of type conversion, what types does @Expiration support?

I see long being tested in the PR, but it would be nice if it supported things like Instant and Duration.