Do not cache condition IDs results from CalCat

The matching condition IDs as a function of PDUs and condition parameters are not constant and should hence not be cached. Due small float deviations, newly injected CCVs may have different condition IDs. CalCat takes allowed deviations into account when sorting by time and thus will always return the condition with the latest CCVs within them. When they are being cached however, this can and did cause recently processed constants to not be retrieved.

@hammerd

Just now I saw that comment in the first line of that method

Thanks for locating this issue. I did suspect that I had made too many assumptions about cacheability. The now deprecated comment could be replaced with comment about why not to cache.

merged

mentioned in commit 8a031302