[c++] Integrate SOMAColumn: Arrow adapter methods, part 1

[XanthosXanthopoulos]

This PR replaces the Arrow schema to TileDB schema transformation to use the SOMAColumn create methods.
Also there are a set of new data converters from arrow arrays to std::array for simplification.

This migration also enforces a current domain restriction for string dimensions to libtiledbsoma in addition to the restriction being present only on the R and Python APIs.

[nguyenv]

Can you explain what the Skip and Take are for and document it? It looks like Take is the index of the column to retrieve and Skip is relevant only for geometry columns (where it's always 2)?

Also is there a way to use std::variant or a templated type instead of std::any or would that make things too complicated?

[nguyenv]

Suggested change

	/**
	* Return a copy of the data in a specified column of an arrow table.
	* Complex column types are supported. The for each sub column are an
	* std::array<T, 2> casted as an std::any object.
	*/
	/**
	* Return a copy of the data in a specified column of an arrow table.
	* Complex column types are supported. The type for each sub column is
	* an std::array<T, 2> casted as an std::any object.
	*/

[XanthosXanthopoulos]

Skip and Take are used in 2 places with 2 specific sets on values (either Skip=3 and Take=2 or Skip=0 and Take=2) and are independent of the geometry column. Their usage is to extract specific subranges of ArrowArray data and they come in handy during ArrowSchema -> TileDBSchema where the arrow array provided has 5 values per dimension and we only need the last 2 to set the current domain.

As to using std::variant, adding more SOMAColumn types would require changing multiple variants. The use of std::any here is to enable runtime polymorphism and indirectly introduces a runtime type check (via any_cast, make_any) between the templated function and the actual dimension type. std::variant can provide all the above it is just a different style I am open to discuss further.