Consolidate sandbox, node, p2p-bootstrap etc into single binary

[charlielye]

It currently just runs and has a MODE env var. It's fine for certain things to be set in the environment as CLI arg alternatives, but this should be an application much like other network binaries. i.e. it accepts commands to define which subsystems are enabled.

e.g.

• aztec --sandbox
• aztec --sequencer
• aztec --sequencer --prover
• aztec --p2p-node
• aztec --pxe
• aztec --pxe --p2p-node

Obviously sandbox is mutually exclusive, but i think other subsystems are/should be optional?

TLDR: Use commander to make our aztec binary more intuitive.

[charlielye]

I would add, don't just blindly implement the above. Might be worth having a discussion around what the best cli api is.
e.g.?
aztec start --sequencer [sequencer-options] --prover [prover-options] --pxe [pxe-options]
aztec cli subcommand [--options]
aztec sandbox

program
  .command('start')
  .description('Start various processes')
  .option('--sequencer [options]', 'Start the sequencer with options (e.g., "--sequencer option1=value1,option2=value2")')
  .option('--prover [options]', 'Start the prover with options')
  .option('--pxe [options]', 'Start PXE with options')
  .action((options) => {
    if (options.sequencer !== undefined) {
      const sequencerOptions = parseOptions(options.sequencer);
      // Start sequencer logic here with sequencerOptions
    }
    if (options.prover !== undefined) {
      const proverOptions = parseOptions(options.prover);
      // Start prover logic here with proverOptions
    }
    if (options.pxe !== undefined) {
      const pxeOptions = parseOptions(options.pxe);
      // Start PXE logic here with pxeOptions
    }
  });```

[PhilWindle]

Proposed cli commands:

aztec cli subcommand [options] // execute the cli app
aztec sandbox // spins up complete sandbox
aztec start --pxe [options] // run pxe, config points to seperate 'node'
aztec start --archiver [options] // just runs the archiver

aztec start --node [options] 
	// runs a 'node'
	// contains merkle trees + p2p enabled tx pool by default
	// must be configured with an archiver url
	// the above gives everything required by a pxe to be a 'public node'
	
aztec start --node [options] --archiver [options] // as above but with own archiver

aztec start --node [options] --sequencer [options] // node, sequencer, remote archiver
aztec start --node [options] --prover [options] // node, prover, remote archiver
aztec start --node [options] --sequencer [options] --prover [options] // node, sequencer, prover, remote archiver
aztec start --node [options] --archiver [options] --sequencer [options] --prover [options] // The full server-side stack

aztec start --pxe [options] --node [options] --archiver [options] // run a pxe alongside my own local node

aztec start --p2p-bootstrap [options]