Start standalone using spacetime start

[jdetter]

Description of Changes

• This enables users to start a new spacetime server instance via: spacetime start
• standalone is now a default feature for the spacetimedb-cli crate, if this feature is enabled then standalone will be compiled into the cli. If this feature isn't enabled then spacetime start will not work but will substantially speed up the compilation time of the spacetimedb-cli crate.

This command contains all of the options that were previously available in spacetimedb start, plus some options that I've added for convienence. The help section is explicit about its operation:

boppy@boppy-macbook SpacetimeDB % cargo run -- start --help
Starts a standalone SpacetimeDB instance. This command recognizes the following environment variables: 
	SPACETIMEDB_LOG_CONFIG: The path to the log configuration file. 
	SPACETIMEDB_LOGS_PATH: The path to the directory that should contain logs for SpacetimeDB. 
	STDB_PATH: The path to the directory that should contain the database files for SpacetimeDB. 
	SPACETIMEDB_JWT_PUB_KEY: The path to the public jwt key for verifying identities. 
	SPACETIMEDB_JWT_PRIV_KEY: The path to the private jwt key for issuing identities. 
	SPACETIMEDB_TRACY: Set to 1 to enable Tracy profiling.

Warning: If you set a value on the command line, it will override the value set in the environment variable.

Usage: spacetime start [OPTIONS] [database_path]

Arguments:
  [database_path]  The path to the directory that should contain the database files for SpacetimeDB (STDB_PATH) [default: /Users/boppy/.spacetime/stdb]

Options:
  -l, --listen-addr <listen_addr>
          The address and port where SpacetimeDB should listen for connections. [default: 127.0.0.1:3000]
      --log-conf-path <log_conf_path>
          The path of the file that contains the log configuration for SpacetimeDB (SPACETIMEDB_LOG_CONFIG) [default: /Users/boppy/.spacetime/log.conf]
      --log-dir-path <log_dir_path>
          The path to the directory that should contain logs for SpacetimeDB (SPACETIMEDB_LOGS_PATH) [default: /Users/boppy/.spacetime]
      --allow-create
          Allows for the creation of files and directories that don't exist
      --enable-tracy
          Enable Tracy profiling (SPACETIMEDB_TRACY)
      --jwt-pub-key-path <jwt_pub_key_path>
          The path to the public jwt key for verifying identities (SPACETIMEDB_JWT_PUB_KEY) [default: /Users/boppy/.spacetime/id_ecdsa.pub]
      --jwt-priv-key-path <jwt_priv_key_path>
          The path to the private jwt key for issuing identities (SPACETIMEDB_JWT_PRIV_KEY) [default: /Users/boppy/.spacetime/id_ecdsa]
  -h, --help
          Print help

Run `spacetime help start` for more information.

You can start a new instance of spacetimedb with just:

spacetime start --allow-create

Internally our developers may find it useful to create another database via:

spacetime start --allow-create "~/.spacetime/another_database"

API

• This is a breaking change to the module API
• This is a breaking change to the ClientAPI
• This is a breaking change to the SDK API

If the API is breaking, please state below what will break

[cloutiertyler]

LGTM

[dbrinkmanncw]

I've tested this with the changes and it no longer requires the $HOME env variable