Counterintuitive handling of relative paths in CLI tool

[jmcph4]

As of b1e0a9d, Artemis' CLI tool exhibits counterintuitive behaviour when given relative directories as roots for generating strategies from templates:

$ uname -a
Linux mybox 5.10.0-23-rt-amd64 #1 SMP PREEMPT_RT Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux
$ pwd
/home/johndoe
$ mkdir -p foo/bar
$ cd foo/bar
$ git clone git@github.com:paradigmxyz/artemis.git
$ cd artemis
$ git rev-parse HEAD
b1e0a9dc4b7ad9bcd7649a022fff3356926cdf19
$ cd bin/cli
$ cargo run -- --strategy-name mystrat ~/foo/bar
$ tree -L 1 ~/foo
foo
├── bar
└── barmystrat

A reasonable user would expect:

$ tree -L 2 ~/foo
foo
└── bar
    └── mystrat

[jmcph4]

Closed by #33.