Remove all state from default stateConfig.json

[nedsalk]

The stateConfig.json file currently is populated mainly because of the old testing approach so that we could use multiple wallets in parallel and avoid the "trying to spend already spent UTXO" issue. Once #2698 is finished, all the coins and messages can be removed because we have full control of the initial state of the chain via the launchTestNode interface. This will still break some tests, like this one, which were relying on that state.

It's important to note that the fuels.config.ts's privateKey property is also set to match one of the owners in the current stateConfig.json and it'll break once the initial state is removed. This stateConfig.json population logic should then be moved into the fuels cli so that we don't have a breaking change here. The utility launchNode gives users the ability to define their own stateConfig.json, so that can be utilized.

[petertonysmith94]

@nedsalk do you think this could be related to the following discussion - points 3 & 5?

[arboleya]

Blocked by:

• Integrate launchTestNode in remaining packages  #2698

[petertonysmith94]

This might break the templates, which uses the faucet referenced by the private key 0x01.

[nedsalk]

@petertonysmith94 The templates use autoStartFuelCore under the hood, and there we can pass a custom stateConfig into launchNode and give coins to private key 0x01 so that no breaking happens.