[c++] SOMAColumn part 1

[XanthosXanthopoulos]

SOMAColumn provides an abstraction over TileDB attributes and dimensions and exposes a common interface for all columns regardless of type. Subclasses of SOMAColumn can implement complex indexing mechanism through additional dimensions and encapsulate all that logic in one place and make it modular.

Subsequent PRs will add implementation for dimension and attributes.

Throughout this PR there is extensive use of std::any to enable polymorphism with the different SOMAColumn types while maintaining a templated interface at the abstract SOMAColumn.

Currently there are 3 types of SOMAColumn:

• SOMAAttribute wraps a TileDB Attribute and an optional enumeration
• SOMADimension wraps a TileDB Dimension and provides methods to access and manipulate the current domain and set the extend for queries
• SOMAGeometryColumn wraps a set of TileDB Dimensions as well as an Attribute and provides methods to access and manipulate the current domain and set the extend for queries

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.09%. Comparing base (00163a7) to head (a58361a).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3329      +/-   ##
==========================================
+ Coverage   85.99%   86.09%   +0.09%     
==========================================
  Files          55       55              
  Lines        6221     6221              
==========================================
+ Hits         5350     5356       +6     
+ Misses        871      865       -6     

Flag	Coverage Δ
python	86.09% <ø> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
python_api	86.09% <ø> (+0.09%)	⬆️
libtiledbsoma	∅ <ø> (∅)

[jp-dark]

These don't match the function template parameter/parameter names.

[johnkerl]

This looks like interesting work but it's not clear why it's being done.

You need a GitHub issue, or Shortcut link, in the description field.

From your GitHub branch name I can discover a Shortcut story number -- since this is an open-source project, please include within a GitHub issue the context that is necessary for anyone who is not a TileDB employee to understand what changes you're making here, and why.

This PR introduces new code without any unit tests, and no callsite from existing code that would exercise existing unit tests. It could be stamped now with guarantee of unit-test cases to follow, but, I'd be happier if you could offer at least a minimal set of tests.

[johnkerl]

Please say what this class is for, what problem it solves. This comment, as is, doesn't tell anything that class SOMAColuimn { ... } doesn't.

In particular, up until there's been a 1-1 mapping of one soma column -> one tiledb dim or one tiledb attr. Here it appears (I'm still reading but it appears so far) that you are allowing for one-to-many mappings of one soma column -> more than one tiledb dim and/or more than one tiledb attr. A top-of-file comment here would need to explain this in at least several sentences' worth of detail.

[johnkerl]

"iff" is specialist mathematical jargon that non-mathematicians are unlikely to recognize. Please don't use it.

[johnkerl]

Suggested change

	* @param if_not_empty Prevent changing an "empty" selection of all columns
	* @param if_not_empty Prevent changing an empty selection of all columns

[nguyenv]

Should we take in a tiledb::Context or SOMAContext?

[XanthosXanthopoulos]

This PR has been split into #3424 , #3425 , #3426 and #3427.