Allow to dynamically provide TTL configuration

[Koooooo-7]

Fix issue: #1433 .

Give users a chance to change the ttl dynamically and give them the flexibility to do so.

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[mp911de]

Using a context-less supplier doesn't add much value here. I could well think of a case, where the TTL could be computed from the actual object.

How about a design of a TTL function (Function<Object, Duration>) where the object argument is provided by the actual cache value?

[mp911de]

A Supplier doesn't make much sense as it just defers the decision on TTL without adding much contextual value.

[Koooooo-7]

Hi @mp911de , I agree with that we should provide some context for user to get the ttl and I did the updates.
And the changes:

1. For now I provide the original key and value to users instead of createAndConvertCacheKey.
2. About the public Duration getTtl() {} for backward compatibility， I user the Object.class as the default key instead.

[mp911de]

Thank you for your contribution. That's merged and polished now.