WIP [base-node] Exit if unable to validate RandomX headers due to memory issues

[delta1]

Description

• attempting to fallback to default flags for randomx dataset and vm creation
• return errors on randomx creation failures
• don't ban sync peers on randomx creation error since it's a local issue
• base node state machine shuts down
• improved logging for randomx creation and errors
• WIP get whole base node to shut down

Motivation and Context

When attempting to run the base node and sync headers with less than 2080MiB of RAM, creation of the RandomX dataset fails and it's not possible to validate the block headers. Node is then stuck in a sync loop.

How Has This Been Tested?

Running base node in a VM with 1GB RAM

Sample Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/focal64"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"
  config.vm.synced_folder ".", "/home/vagrant/base_node", :mount_options => ["dmode=777", "fmode=777"]

  config.vm.provider "virtualbox" do |vb|
    vb.cpus = 2
    vb.memory = "1024"
  end
end

Checklist:

• I'm merging against the development branch.
• I have squashed my commits into a single commit.

[StriderDM]

Fixed here:
#3301