Exceptions should include "context details" when provided

[jshook]

It is useful to have diagnostic data provided directly from an exception that would otherwise require a user to manually dig into related configurations or other data sources.

Examples of this:

• The details for a database which returned an error.
• The UTC timecode of the error.
• Client system profile (CPUs, memory, ..)

Other details like java details, like heap utilization, etc. should generally be left out of such info, since this is properly metrics data which is provided in other places.

Because error handling mechanisms and semantics must remain robust, any mechanism which adds context to an exception must not throw any errors itself.

A new decorator type NBErrorContext should be added which indicates it can add error details in the form of a Map<String,String>. When an exception is thrown, the main error handling logic should walk the stack to find any such instances, and if present, the exception should be appended with ;; additional context: and the details of the error.

[jshook]

Elements which have important context for interior stack frames should be decorated with this. This includes activities, or spaces which are invoked during the execution of an operation.

[dave2wave]

1. Details of the tenant come from the driver. Is tenant enough for Astra or is there more metadata like region?

[dave2wave]

2. Can we indicate if the error is client or serverside?
3. UTC time should always prepend the ERROR. Make it look more like an access log.

[jshook]

The details found in this way need to be added to the status.yaml