Do COMPUTE STATS on ACID tables in a "proper" transactional way

IMPALA-8836's goal is just to get the stats in somehow in a way that Impala can use them and Hive does not treat them as accurate. It would be the best if the SELECT(s) that are behind the COMPUTE STATS would use the same validWriteId list, and the stats would be set with the same writeId list to express that the stats are based on that state of the table. Theoretically Hive uses this mechanism to decide whether the stats are up to data by comparing a SELECTs validWriteIdList with the one saved for stats and considers it stale if the SELECT sees new writeIds.