ClusterReplication drivers are saving erroneous expiration date in low-level backends

[Geolim4]

Configuration

• PhpFastCache version: "8.x, 9.x"
• PhpFastCache API version: "3x, 4x"
• PHP version: "Irrelevant"
• Operating system: "Irrelevant"

Describe the bug

The ClusterFullReplication and ClusterSemiReplication are saving erroneous expiration date in low-level backends. The saved date is a now date, not a now + "defaultTtl" date

[github-actions]

Hello curious contributor !
Since it seems to be your first contribution, make sure that you've been:

• Reading and searching out our WIKI
• Reading and agreed with our Code Of Conduct
• Reading and understood our Coding Guideline
• Reading our README
  If everything looks unclear to you, tell us what 😄
  The Phpfastcache Team

[Geolim4]

Stupid bot, who the hell coded you ?

[Geolim4]

Will be fixed in 8.1 and 9.1.

The 9.1 release will immediately follow the 9.0.2.