Add a friendly panic hook

[Quantumplation]

A block producing node, and Amaru, is considered "mission critical" software, for the following reasons:

• The network is relying on the availability and correctness of each alternative implementation in proportion to its stake
• The stake pool operators are (i.e. eventually will be) relying on the continuing functioning of the block producer as a form of income

For that reason, the node should never just hard "crash"; even in error cases, the node should respond to these bad conditions in a more graceful way, perhaps eventually even including raising an alarm via any metrics / alerting systems built into the node.

Therefore, we install a panic hook; if a crash does arise in the wild, we'd love a bug report, so we can address it more appropriately. For that reason, we want to make the process to open the issue as welcoming as possible.

Here's what it looks like for an explicit panic:

Here's what it looks like for an implicit panic, like divide by zero:

Here's what it looks like for a contextual panic, like .expect():

I included a commit in the history with an explicit panic; if you want to test it yourself, you can checkout e9bfdf5931ff6b093e830bf0252c6be29eaa7372 and run cargo run daemon --peer-address 127.0.0.1.

Note that I borrowed a lot of code from Aiken; For this PR, I just included the needed utility functions in the panic.rs file, but we might want to pull some of these into their own files / modules, as they are in Aiken.