static redis keys for entity

Before BeeORM was using entity structure to generate redis key. So when entity structure was changed, for example,
new column was added after deploy all entity redis keys were different. Now BeeORM uses only entity full name to calculate redis key hash.

Imagine this scenario - two applications are using the same entity - UserEtity. The developer added new column to this entity and deployed code on applications #1 and #2. All worked as expected, new redis keys are used so all queries with this Entity loaded data from Mysql and filled redis cache. Is not required to clear redis after deploy.

But now imagine developer deployed code only in application #1 but forgot to deploy it in application #2 (it happened today for instance in one of the projects). Then i application #1 all keys are invalid ad cache is filled with new data but inapplication #2 uses still all keys. So changes in one application are not visible and applications are broken.

Solution is to always deploy applications that the same entities at the same time or simply switch to this version of BeeORM.
In this version reids key is build based on enity name. So even if you forgot to deploy code in in applications #2 damage is much smaller. data is updated in both applications in cache but you will start seeing new type of errors, for example applications #2 is getting data from cache with new column and can't unserialize it. But it's better to do it this way, less evil.