No way to supply --runstate-dir on edgedb init

When trying to setup an EdgeDB instance on a limited environment; EdgeDB throws this warnings,

$ ~/.edgedb/bin/edgedb server init --nightly default
...
2020-12-20T11:44:34.0903426Z CRITICAL 6748 2020-12-20 11:44:34,089 edb.server: cannot create the runstate directory: '/run/user/1001' does not exist; please use --runstate-dir to specify the correct location

but I couldn’t find how to pass this as an option;

 $ ~/.edgedb/bin/edgedb server init --runstate-dir x --nightly test
error: Found argument '--runstate-dir' which wasn't expected, or isn't valid in this context

If you tried to supply `--runstate-dir` as a PATTERN use `-- --runstate-dir`

USAGE:
    edgedb server init [FLAGS] [OPTIONS] <name>

For more information try --help

or

 $ ~/.edgedb/bin/edgedb --runstate-dir server init x --nightly test 
error: Found argument '--runstate-dir' which wasn't expected, or isn't valid in this context

If you tried to supply `--runstate-dir` as a PATTERN use `-- --runstate-dir`

USAGE:
    edgedb [FLAGS] [OPTIONS] [SUBCOMMAND]

For more information try --help

[tailhook]

By the way, looking at original issue: https://github.com/reizio/reiz.io/pull/24 (/cc @isidentical )

1. You may use edgedb/setup-edgedb github action to install edgedb
2. Not having XDG_RUNTIME_DIR means you don’t have systemd user daemon too, as far as I remember. You may try:

   edgedb init --start-conf=manual default
   edgedb server start --foreground default
   

   (i.e. running server as a subprocess rather than service and backgrounding via shell)
3. We may want to create edgedb/run-edgedb github action to run a server (and configure credentials)

[tailhook]

@haikyuu two posible workarounds:

1. Do as edgedb-js (temporary runtime dir, and propagate it to the actual test manually)
2. Set env: {XDG_RUNTIME_DIR: "${{ runner.temp }}/edgedb"} in the environment, covering all actions that touch edgedb and client apps (e.g. root of your workflow or a job)