Smarter resize buffer and algorithm resizing in IndexedTable

[npawar]

The resizer has a very naive logic at the moment to decide the buffer capacity:
From BaseTable.java:

// TODO: tune these numbers
      // Based on the capacity and maxCapacity, the resizer will smartly choose to evict/retain recors from the PQ
      if (capacity <= 100_000) { // Capacity is small, make a very large buffer. Make PQ of records to retain, during resize
        _maxCapacity = 1_000_000;
      } else { // Capacity is large, make buffer only slightly bigger. Make PQ of records to evict, during resize
        _maxCapacity = (int) (capacity * 1.2);
      }

This allocation is unfair for numbers which fall on the borderline. We need smarter formulas for computing this.

The resize algorithm (in TableResizer) also needs a revisit and enhancement

[xiangfu0]

Closing — this has been implemented in PR #4728, with further improvements in PR #7373, #7420, and #14620. IndexedTable resize buffer now has configurable initial capacity.