Change API surface to return a KacheResult<S, E> result class instead of relaying on try-catch

[pablichjenkov]

Is your feature request related to a problem? Please describe. Consumer App code gets a bit hard to read with so much try/cath. This is a readability preference.

Describe the solution you'd like Return a KacheResult<T, E> that will have the cached value when successful and a specific family of errors when not. Errors could be, from IO errors like CacheCorrupted, or time errors like CacheExpied, or capacity errors like EntryRemovedDueToCapacityLimit