Add --path flag

[ordepdev]

This change allows us to provide a directory for creating and loading both corral.json and dep-lock.json files. It affects most commands as they mostly need to load the file before doing their job. So, from now on, we can pass the --path "path/to/the/bundle/dir/" argument.

corral[master] % mkdir tmp
corral[master] % corral init --path tmp

init: from dir tmp
INFO: Created bundle in /Users/ordepdev/Work/corral/tmp
FINE: Going to write /Users/ordepdev/Work/corral/tmp/corral.json
INFO: Writing /Users/ordepdev/Work/corral/tmp/corral.json
FINE: Going to write /Users/ordepdev/Work/corral/tmp/lock.json
INFO: Writing /Users/ordepdev/Work/corral/tmp/lock.json
INFO: init: created: tmp

Solves #23.

[ordepdev]

So, I took the liberty to include the path parameter in the context with two possible values, either the provided path or the default one, Path.cwd(). It makes things so easy after calling the corresponding command, we just need to use ctx.path everywhere we want to use it.

[SeanTAllen]

@cquinn you are the subject matter expert. Can you give this a review?

[SeanTAllen]

@ordepdev thoughts on tests that can be added with this change?

[ordepdev]

@SeanTAllen I can add tests for creating the corral.json file with a custom path.

Something like this maybe:

class iso _TestCreateBundleInCustomPath is UnitTest
  fun name(): String => "bundle/create-in-custom-path"

  fun apply(h: TestHelper) ? =>
    let log = Log(LvlFine, h.env.err, LevelLogFormatter)
    let expected = FilePath(h.env.root as AmbientAuth, "tmp")?
    match BundleFile.create_bundle(h.env, "tmp", log)
    | let bundle: Bundle =>
      h.assert_eq[String](expected.path, bundle.dir.path)
    end

[SeanTAllen]

@ordepdev do you want to squash this and push so you can control the commit message or shall I squash and merge?

[ordepdev]

You can squash and merge with the first commit message.

[SeanTAllen]

Thanks, @ordepdev.