[C++] Vendor backward for better stack traces

is a neat single-header library which allows capture of very expressive stack traces. It is compatible with c++11 and is cross platform, I think it would greatly improve error reporting in arrow.


In particular, the stack traces provided by a failed DCHECK are much less expressive than they could be and don't include file/line information, while the traces added to statuses by `ARROW_EXTRA_ERROR_CONTEXT` don't include the frame in which the status was constructed- which is frequently the frame which we most need information from. Backward addresses these shortcomings and then some.

**Reporter**: [Ben Kietzman](https://issues.apache.org/jira/browse/ARROW-17311) / @bkietz

_{**Note**: *This issue was originally created as [ARROW-17311](https://issues.apache.org/jira/browse/ARROW-17311). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

Read the backward-cpp proposal and inspect Arrow's existing stack traces for failed DCHECKs and the traces added by ARROW_EXTRA_ERROR_CONTEXT. Determine how backward could be integrated across supported platforms; done means those traces include the file, line, and relevant status-construction frame described in the issue.

Written by the indexing model from the issue text.