Accounts not created in fresh deployment if `accounts.json` exists

[Ivo-Yankov]

Describe the bug

The idempotency guard for skipping the account creation step should be updated. The step should not be skipped if the network nodes did not exist before running the current command.

Also, the solo one-shot single destroy command should delete the deployment directory in the SOLO_HOME directory.

Describe the expected behavior

Accounts should always be created when a new deployment is being created.

To Reproduce

solo one-shot single deploy
solo one-shot single destroy
solo one-shot single deploy

Observe that the accounts were not created for the second deployment

Additional Context

No response

[jan-milenkov]

Are we sure about this one, it was a part of phase 1 @Ivo-Yankov

#4564

[Ivo-Yankov]

Are we sure about this one, it was a part of phase 1 @Ivo-Yankov

Yes, it was part of phase 1, however if the network nodes are being created with the current command, then we cannot assume that the state for the accounts exists. Or maybe we should think of a different condition for the guard, but the current implementation is not correct.