Port new concept of "DPoW confs" from KMD

[leto]

This is a WIP but I wanted to start the conversation. This PR still needs more tests which actually look at rawconfirmations/confirmations result data and a completely new documentation file, describing how to use this new feature, it's ramifications, etc...

TLDR:

• Not a consensus change, nodes can opt-in upgrade to this feature
• This changes how RPCs work, and adds a new key rawconfirmations where-ever there was a confirmations key in response data
• Complete DPoW protection with no code changes or additions
• "Fails closed" in the sense that if notarizations are somehow stopped, confirmations will never go beyond 1
• When dpowconfs is enabled (which it is by default), the old concept of confirmations is stored in rawconfirmations, while dpow-protected confirmations are returned in confirmations, which all exchanges/wallets/etc currently look at
• Upgrading to this does not require a rescan or reindex, just a quick recompile and restart of hushd

It felt heavy-handed to add the entire komodo_utils.h but just grabbing 1 or 2 functions from there led to more dependent functions being necessary, so it was easier to add the entire file.

[leto]

Looks like most stuff from komodo_utils is not needed, because I am doing some unnecessary stuff with komodo_statepointer, so get rid of all that

[leto]

Now that we have passing regtests, I feel this code is ready for dev, we can debug further issues there, were it can be tested with the new getsnapshot code