chore: Remove Status from ArraySchema, Attribute, Dimension, Domain

[rroelke]

There are a number of old stories which refer to "un-Statusing" various parts of the code. I can imagine some benefits of doing this, but a new one concerns our upcoming interoperability with Rust code.

The Rust crate we use to interoperate with C++, cxx, can generate idiomatic bindings in Rust to use types and call functions which are defined in C++. These bindings can declare and use "opaque" types, i.e. types whose definitions reside within C++ and are invisible to Rust code. However, these types cannot be passed by value to and from Rust functions.

Status is commonly used as a return value from our internal C++ code. This prevents us from declaring bindings for those functions in cxx and thus calling them from Rust. We probably cannot migrate Status from an opaque type to a shared type, but we can "un-Status" the functions we want to use.

This pull request "un-Statuses" the methods of classes in the array_schema directory. This will eventually allow them to be called from Rust code.

---

TYPE: NO_HISTORY
DESC: Un-Status array_schema methods

[bekadavis9]

Same as above. Should return bool. I won't continue to mark the rest of these for both of our sake :')

[rroelke]

Only has_dimension and has_attribute have value which can now be return this way, the other affected functions do not have out arguments.

[bekadavis9]

Nit: no need to cast the exception body to std::string. Rings true throughout PR.

[rroelke]

This is needed for the concatenation

[teo-tsirpanis]

Thanks!

[teo-tsirpanis]

Suggested change

	echo "START tiledb_regression"
	./test/regression/tiledb_regression -d yes
	echo "END tiledb_regression"
	echo "START tiledb_regression"
	./test/ci/test_assert -d yes
	echo "END tiledb_regression"
	echo "START tiledb_unit"
	./test/tiledb_unit -d yes "~[rapidcheck]" | awk '/1: ::set-output/{sub(/.*1: /, ""); print; next} 1'
	echo "END tiledb_unit"
	echo "START unit_vfs"
	./tiledb/sm/filesystem/test/unit_vfs -d yes | awk '/1: ::set-output/{sub(/.*1: /, ""); print; next} 1'
	echo "END unit_vfs"
	# Run rapidcheck tests as their own process so we can see the random seed for each
	./test/tiledb_unit --list-tests "[rapidcheck]" --verbosity quiet | while IFS= read -r testname; do
	echo "START tiledb_regression"
	./test/regression/tiledb_regression -d yes
	echo "START tiledb_regression"
	./test/ci/test_assert -d yes
	echo "START tiledb_unit"
	./test/tiledb_unit -d yes "~[rapidcheck]" | awk '/1: ::set-output/{sub(/.*1: /, ""); print; next} 1'
	echo "START unit_vfs"
	./tiledb/sm/filesystem/test/unit_vfs -d yes | awk '/1: ::set-output/{sub(/.*1: /, ""); print; next} 1'
	# Run rapidcheck tests as their own process so we can see the random seed for each
	echo "START tiledb_unit rapidcheck"
	./test/tiledb_unit --list-tests "[rapidcheck]" --verbosity quiet | while IFS= read -r testname; do

We don't need both start and end messages, since starting an operation implies that the previous one ended.

[teo-tsirpanis]

Nothing to do for this PR, but the format of our error messages has lots of room for improvement.

[teo-tsirpanis]

Suggested change

	if (std::isinf(domain[0]) || std::isinf(domain[1])) {
	throw DimensionException("Domain check failed; domain contains NaN");
	}
	if (std::isnan(domain[0]) || std::isnan(domain[1])) {
	throw DimensionException("Domain check failed; domain contains NaN");
	}
	if (!(std::isfinite(domain[0]) && std::isfinite(domain[1]))) {
	throw DimensionException("Domain check failed; domain cannot contain NaN or Infinity");
	}