Remove Status_StorageManagerError and Migrate group_metadata_vacuum out of StorageManager.

[bekadavis9]

Remove Status_StorageManagerError and its occurrences.
Related subsequent fixes:

• Remove Logger::status_no_return_value and replace occurrences with Logger::error.
• Remove Status and std::optional from returned tuple of Array::open_for_writes.
• de-Status Context::init_loggers.
• Migrate StorageManagerCanonical::group_metadata_vacuum -> static Group::vacuum_metadata.

[sc-48630]
[sc-48639]

---

TYPE: NO_HISTORY
DESC: Remove Status_StorageManagerError and Migrate group_metadata_vacuum out of StorageManager.

[eric-hughes-tiledb]

One change for which exception to throw needed.

Also, we should make stories for removal of StorageManager for (1) class Array and (2) Consolidator::create.

[eric-hughes-tiledb]

Needing to make a new storage manager just to call Consolidator::create is quite a red flag. The problem isn't in this code narrowly, though; it's the implementation of the consolidator.

We should target changing Consolidator::create for a refactor. It should be possible to convert it to ContextResources and RestClient, but it will also entail changing a constructor signature for Array. It's definitely going to require a concerted effort. Removing all the array and group functions from StorageManager should happen first.

[bekadavis9]

There's already a followup story to remove usage of StorageManager from the consolidation code: https://app.shortcut.com/tiledb-inc/story/47947/eliminate-storagemanager-arguments-in-consolidation-code-in-favor-of-contextresources

[eric-hughes-tiledb]

LGTM

[KiterLuc]

Merging with the unit URI failures as they are unrelated. [sc-https://app.shortcut.com/tiledb-inc/story/48975/intermittent-segfaults-in-unit-uri-on-windows]