feat: Add support for callable TTLs in cache handlers

[patel-vansh]

Description
This PR adds support for callable for TTL in cache handlers.

Many times the following two cases arise while calculating TTLs:

• Calculating TTL is expensive operation
• TTL depends on the return value of the callback function (for e.g, cache until the first item's expires_at is reached).

In the first senario, calculating TTL everytime, even if its a cache hit, is redundant. And in second senario, you can't just use the remember() method. You have to rely on traditional get()/save() methods.

This PR solves both problems by adding support for callables as TTL. The passed callable may optionally accept the computed value as first parameter which solves the second senario.
And by passing callable without any parameter just defers calculating TTL until cache miss.

This can be considered as a Breaking Change as the Interface method's signature is changed. However, the usage of remember() method remains mostly unchanged.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[patel-vansh]

Both failing checks are unrelated to the changes in this PR.

[paulbalandan]

Last fix and we're good.

[paulbalandan]

Thanks!

[michalsn]

Suggested change

	$cache->remember('key', static fn () => 60, static fn () => fetchData());
	$cache->remember('key', static fn ($value) => 60, static fn () => fetchData());

[michalsn]

Considering changes made, shouldn't this be:

The callable always receives the computed value as its first argument

[patel-vansh]

Actually, my initial thought was to support both 0 parameters and 1 parameter callables. The recent changes was just more of a refactor and avoiding the use of Reflection class, not a restriction to always having first argument in callable. That's why the current user guide and docs explicitly states that both cases are valid. But if its misleading, I will change it.