Update version/history for 2.3.1 (TileDB-Inc#2385)

Update version/history for 2.3.1 (TileDB-Inc#2385)

Annotate consolidation/vacuum timestamp config parameters as experime…

…ntal (TileDB-Inc#2325) (TileDB-Inc#2326)

We are not certain that we want to commit to configurating the consolidation
and vacuuming timestamp bounds in the config object. Mark them as experimental.

---

TYPE: NO_HISTORY

Co-authored-by: Joe Maley <[email protected]>

Co-authored-by: joe maley <[email protected]>
Co-authored-by: Joe Maley <[email protected]>

Fix ch7908: missing assignment for adjust_range_oob_func_ in a Dimens…

…ion constructor (TileDB-Inc#2314) (TileDB-Inc#2317)

Co-authored-by: Isaiah Norton <[email protected]>

Prepare 2.2.9 release (TileDB-Inc#2256)

Co-authored-by: Joe Maley <[email protected]>

Additional release 2.2.8 notes (TileDB-Inc#2232)

Co-authored-by: Joe Maley <[email protected]>

Optimize `Subarray::compute_relevant_fragments` (TileDB-Inc#2218)

This patch refactors `Subarray::compute_relevant_fragments` to reduce the time
complexity at the expense of false-positive relevant fragments. The correctness
of the tile overlap computation is unaffected because it will not find overlap
within falsely relevant fragments.

Currently, this routine has a time complexity of:
`<# dimensions>[product]<# dimension ranges> * <# fragments>`

This patch modifies the routine to have a time complexity of:
`<# dimensions>[summation]<# dimension ranges> * <# fragments>`

Currently, a single relevant-fragment-bytemap is computed by checking overlap
on each fragment's ND-range against the ND-range for each flattened range
ids.

This patch maintains an individual relevant-fragment-bytemap for each
dimension, where the bytemap is computed by checking overlap on each fragment's
ND-range against each ND-range in subarray. The final relevant-fragment-bytemap
is computed by performing a logical AND among each dimension's individual
fragment bytemap.

The important consideration is that the input to this routine is a start/end
index on the flattened range ids. To reduce risk, this change does not modify
the interface to `Subarray::compute_relevant_fragments`. To compute in ND-space
instead of flattened-space, we must convert the input start/end indexes to
ND-coordinates. The ND space between the start/end coordinates is not guaranteed
to encapsulate all ranges in between the flattened ("total order") start/end
indexes. To handle this, we must expand the coordinates to sufficiently capture
all input ranges. This may add additional ranges, which may result in false
positive relevant fragments.

---
TYPE: IMPROVEMENT
DESC: Optimize `Subarray::compute_relevant_fragments`

Co-authored-by: Joe Maley <[email protected]>

2.2.7 release notes, version update (TileDB-Inc#2155)

Co-authored-by: Joe Maley <[email protected]>

Update HISTORY and version to 2.2.6

Fix consolidated fragment metadata parsing (TileDB-Inc#2135)

* Fix consolidated fragment metadata parsing

Currently, all footers in consolidated metadata files are parsed with the format
version of the consolidated metadata file. This patch ensures that footers are
parsed with the version stored in the footer.

In practice, this can fix one potential error when opening an array:
TileDBError: [TileDB::ConstBuffer] Error: Read buffer overflow

---
TYPE: BUG
DESC: Fixes a potential crash when opening an array with consolidated fragment metadata

* Update HISTORY.md for TileDB-Inc#2135

Co-authored-by: Joe Maley <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>