Ignite-backed caches may exceed configured limits about aldica

[AFaust]

I forgot to close this issue because I forgot that it is actually the intended behaviour, The configured limit in Ignite caches only applies to on-heap cache entries. The amount of off-heap cache entries is only limited by the configured limit on off-heap memory regions, which is defined by amount of bytes, not number of entries. The display in OOTBee Support Tools is of course unaware of that and might be confusing (apparently event to me at the end of a year), but our documentation actually mentions that:

The amount of data an individual cache is allowed to store cannot be restricted apart from assigning that cache to a dedicated storage region.