[C++] Determine strategy for propagating failures in initializing built-in function registry in arrow/compute

[asfimport]

As discussed on #7240, we are using DCHECK_OK to check statuses when initializing the built-in registry.

We could propagate failures by changing arrow::compute::GetFunctionRegistry to return Result, but there may be other ways

Reporter: Wes McKinney / @wesm

Related issues:

• [C++] C++ array kernels framework and execution buildout (umbrella issue) (is a child of)

_{Note: This issue was originally created as ARROW-8897. Please see the migration documentation for further details.}

[thisisnic]

This issue hasn't had activity in a long time. If it's still being worked on, please leave a comment. Otherwise, it will be closed on 23rd June.

Labelled Status: Stale-Warning for tracking.