Cocona not expanding path parameter when CLI argument is given with equal sign

[tkiapril]

Upon researching with @longfin, we found that when giving the CLI argument in a form like --ARG=~/example (e.g. for --store-path argument,) Cocona does not expand path parameter correctly. Thus, when --store-path is given with the equal sign(=), store is not loaded appropriately and thus say that there are no chain IDs. (When the process is inturrupted while preloading in this situation and is run again, it results in System.Collections.Generic.KeyNotFoundException: The given key ...

As bash expands ~, when the parameter is given in the form of --ARG ~/example, it is run correctly. Thus, we should check if the given path argument can be expanded. cc @dahlia

[dahlia]

We could send a patch to Cocona so that it expands metacharacters like ~ and *, but I guess the maintainer would not accept such change. In Unix tradition, path expansion always has been up to shells rather than each application. (It's quite opposite in DOS and Windows though.) It's also confusing if --arg=~/foo means --arg="$HOME/foo" or --arg=./~/foo.