[testing] Validate node bootstrap for mainnet and testnet

[marun]

Enable testing of bootstrapping in full sync (non-archival) and state-sync configurations for both mainnet and testnet.

Notes

• public github workers only support a maximum of < 30GB of disk which is insufficient for mainnet or testnet nodes
• prefer kubernetes deployment to avoid having to deal with host provisioning (e.g. ec2)
  • suggest deploying one pod to run the test and the test pod can deploy the node as another pod
• pruning is enabled by default ({"pruning-enabled": true})
• state-sync is enabled by default for nodes with an empty db ({"state-sync-enbled": true})

[marun]

Status update:

• state-sync testnet passed in ~18.5h without extra storage on a runner with 8 vcores / 16GB of ram
• still waiting on full-sync testnet, a couple of initial attempts failed due to infra failure and timeout. The currently running job completing successfully depends on being able to complete within the 5 day limit for a job on a self-hosted runner and requiring < 200GB of storage
• still waiting on a runner with a PVC with more than 200GB of storage, which precludes testing mainnet.
• based on expected execution duration for a testnet full-sync bootstrap, it seems doubtful that a mainnet full-sync bootstrap can succeed within the 5 day limit and will require bespoke scheduling.

[github-actions]

This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.