Update RegTest Settings - Taproot Test

[JaredTate]

These settings allowed for me to step through a complete taproot signaling and activation window soft fork process on regtest. The way taproot softwork will work according to BIP 9 is as follows:
https://en.bitcoin.it/wiki/BIP_0009

With each block and soft fork, we associate a deployment state. The possible states are:

DEFINED is the first state that each soft fork starts out as. The genesis block is by definition in this state for each deployment.

STARTED for blocks past the starttime.

LOCKED_IN for one retarget period after the first retarget period with STARTED blocks of which at least threshold have the associated bit set in nVersion.

ACTIVE for all blocks after the LOCKED_IN retarget period.

FAILED for one retarget period past the timeout time, if LOCKED_IN was not reached.

I can 100% confirm our taproot activation will work. All tests passing for taproot code.

There we have it . The taproot activation process: "defined" -> "started" -> "locked_in" -> "active". Successful activation on regtest.

Note:
So the way activation works is on Jan 10th the network will say "started". If 70% of blocks get mined supporting taproot in a rolling 1 week period then it will switch to "locked_in" then 1 week after it will be "active". This could take weeks or months. We need 70% of miners to agree.

Once active the GUI will not allow users to send taproot txs though. This functionality was not added until BTC v23 when a drop down selection was added. 3 versions after taproot code was introduced and after activated on BTC.

Prior to that taproot tx's on BTC v22 could only be created manually with outside scripts as detailed here: https://www.reddit.com/r/Bitcoin/comments/r37ky5/howto_create_and_use_a_taproot_wallet_on_testnet/

So once DigiByte activates taproot we will need to release another version of DigiByte Core v8.23 that allows users to use taproot addresses in the GUI.