Add a timeout flag for the network command destroy subcommand

[jeromy-cannon]

Per Alex Kuzmin, when there are pods currently in Pending state, then the following command:

solo network destroy --namespace "${SOLO_NAMESPACE}" --delete-pvcs --delete-secrets --force

will run/hang indefinitely.

Note: he is using the taskfile.yaml clean target in the examples folder. So we should update the [solo:network:destroy](https://github.com/hashgraph/solo/blob/ec63a659ae325ab1631409a76e6894deccdb0ed4/examples/custom-network-config/Taskfile.yml#L110-L110) target with the recommended timeout also. examples/custom-network-config/Taskfile.yml

Tasks

Preview Give feedback

1. add a --timeout flag to solo network destroy, default it to 120 seconds. If the timeout is reached and it is still running, then abort the command and continue.
2. if the --timeout flag is used and the following 3 flags are also used: --delete-pvcs --delete-secrets --force then when the timeout is reached abort the command and then perform a delete on the namespace, use the timeout on this command too, and abort if it also runs over.
3. log appropriate error messages to the user when the timeout is reached and the command is aborted
4. make sure if the timeout is reached that we still give a non zero return code when exiting
5. update the solo:network:destroy target in examples/custom-network-config/Taskfile.yml to include the new --timeout option

[JeffreyDallas]

So it starts hanging at node stop step, before node destroy step ?

Can you attach ~/.solo/logs/solo.log and also use k9s to check what are status of network pods ?