[Malleability] Update herocache to use generics and implement BackData

[UlyanaAndrukhiv]

Related issues

Main approach for this refactoring - #6703

This issue depends on:

• [Malleability] Update BackData to use generic arguments instead of flow.Identifier and flow.Entity #7070

Context

The current Cache implementation uses specific types such as flow.Identifier for keys and flow.Entity for values, which restricts flexibility and reusability across different data structures. The PoolEntity structure also tightly couples entity (flow.Entity) and the identity (Identity associated with this entity) fields to these concrete types, limiting the overall flexibility. The goal is to refactor the Cache and PoolEntity to use generics, enabling them to handle any data type for both the key and the value.

Additionally, herocache is the implementation of BackData.The task has a dependency on #7070, which should be completed before proceeding with certain parts of the implementation.

Proposed Solution

• Refactor the Cache and PoolEntity to use generics for both theflow.Identifier and flow.Entity types.
  • The PoolEntity will be updated to use generic types instead of flow.Identifier for the key and flow.Entity for the value.
• Ensure the BackData functionality in herocache is implemented.
• Ensure the Pool integrates seamlessly with the new generic Cache and PoolEntity design.

Definition of Done

• The Cache and PoolEntity are refactored to use generics.
• The BackData functionality is implemented within herocache.
• The Pool is updated to work with the new generic Cache and PoolEntity design.
• All relevant code that interacts with the Cache and PoolEntity is updated accordingly.
• Tests are updated or added to ensure the new generic design works as expected.