Fall back to slp-validate

[christroutner]

On July 11th, an SLP transaction was broadcast that made all the SLPDBs stall and stop validating transactions. When this happened, the token-liquidity app stopped being able to identify incoming UTXOs as token UTXOs. This sanity check code was triggered, which at least dropping red flags into the logs.

The scope of this task is to expand the this sanity check code. Instead of the current functionality, the following checks should be conducted:

• slp-parser should be applied to the transaction. If it throws an error, then the UTXO is not an SLP transaction and it can be treated as BCH.
• If slp-parser does not throw an error, then the UTXO may be a token UTXO. The UTXO should be run through slp-validate to manually validate the DAG and ensure this isn't a token UTXO that SLPDB missed.

[christroutner]

Another corner case that effects this scenario is when non-PSF SLP tokens are sent to the token-liquidity app. It will be necessary to call the bchjs.SLP.Utils.tokenUtxoDetails() to verify that the token is actually a PSF token.