Properly resolve user's path

[DeviousStoat]

This implements only the part for the new command, the directory argument and sets up the tooling for the rest I guess.

I was spending way too much time pondering in front of my monitor for the rest. Didn't really want to ask too many questions but I guess I was not moving at all so I will ask. I am very confused about all the path options there is in the Hix.Optparse module. Why some paths are expected to be relative, some other absolute and some other absolute or cwd? Can't they all be absolute or relative to the cwd?
Can't all these and all these be reduced to just a pathUserOption to be resolved later as introduced in this PR (or the sum type you suggested previously if we need for the tests later)?

[tek]

Please don't hesitate to ask questions whenever you need!

When I introduced absPathOrCwdOption rather recently, I only changed a handful of options to use it, but there are likely some more that would benefit from it, so change those if you like.

However, there are some that cannot be absolute paths, because they are used in temporary directories, like the one in stateFileConfigParser (not sure if there are any others – at least rel{File,Path}Option have no other consumers).

[tek]

wanna merge or convert more use sites of the old parsers?

[DeviousStoat]

both? :D I can make another PR

[tek]

alright then 😁