Initialize project problems and solutions

[mvuorre]

I am having great difficulty using and modifying init_vertical_project(). For example, when I run, vertical::init_vertical_project("test"), the new package is not created in test/, but in the directory where I called the function. The fact that there are two different arguments for path and name is also confusing, I tried specifying both but it ended up throwing more errors. (Directory does not exist.)

I have modified the build to just rely on one (simpler, ~50 lines vs ~150 lines) function that works both from GUI and CLI.

EDIT: The suggested solution in dev also removes the interactive query of components when vertical is initiated in CLI (a process that adds unnecessary complexity), and the option to create vertical inside an existing directory. The latter is removed because there's no way to anticipate all the possible files and directories that an existing directory might have, each of which could lead to different errors and warnings. Further, because we cannot programmatically deal with unknown existing files, simply creating the vertical skeleton inside an already potentially complicated project doesn't seem any better than asking the user to move their existing messy stuff to a new vertical project that is outside, rather than inside, the existing project.

[mvuorre]

Further improvements in 03c2b3d

[mvuorre]

Close with #41