support cache_max_entry_count >= 1 for Turbomind backend

[lh9171338]

Motivation

The Turbomind backend already supports cache_max_entry_count >= 1. However, the assertion check was not updated accordingly and still enforces 0 < cache_max_entry_count < 1. This inconsistency prevents valid configurations (e.g., cache_max_entry_count = 50) from being used, even though the backend supports them.

Modification

Relaxed the assertion condition for cache_max_entry_count:

- assert 0 < self.cache_max_entry_count < 1, "invalid cache_max_entry_count"
+ assert self.cache_max_entry_count > 0, "invalid cache_max_entry_count"