Remove all state from default `stateConfig.json`

[nedsalk]

The stateConfig.json file currently is populated mainly because of the old testing approach. Once #2698 is finished, all the coins and messages can be removed. This will still break some tests, like this one, which were relying on that state.

The fuels.config.ts's privateKey property is set to match one of the owners in the current stateConfig.json will break once it's clean. This stateConfig.json population logic should then be moved into the fuels cli. 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:

• https://github.com/FuelLabs/fuels-ts/issues/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.