databases/cego: upgrade 2.44.12 -> 2.44.13

• Further recovery fix in CegoTableManager::insertDataTable In case of an insert exception ( e.g. duplicate pkey ), a checkpoint is forced now after deleteData to ensure file consistency In CegoObjectManager::insertPageData a second checkpoint is forced after data copy, if a previous checkpoint has occured. Otherwise this insert might be ignored during recovery because of lower LSN
• Fix in CegoBTreeManager::checkDuplicate, the check for uflag ( returned CegoBTreeNode::valueExists ) to check for high value is not enough if, entries have been deleted from node. Instead, all subsequent pages have to be checked until a value higher is found
• Introduced CegoBufferPool::getCPCount() to return to current checkpoint count. This method is used by CegoTableManager, CegoObjectManager and CegoTransactionManager to decide, if a consitency checkpoint is required
• Version passed checkCrashRecovery with the following parameters NUMRUN=100 DOTRANSACTION=-dotransaction ARANGE=10000 AINTERVAL=500 ACOUNT=30000 PRIMARY=primary POOLSIZE=191 All relevant checkpoint situations have been observed over all run

Submitted by: Bjoern Lemke <lemke@lemke-it.com>