Adds create-stack command

[ryanmoran]

Summary

Resolves #52

Also, moves top-level tests into integration directory.

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[sophiewigmore]

@ryanmoran I plan on giving this a full review tomorrow, just as an update!

[sophiewigmore]

I have a small suggestion I want to hear your opinion on. I think that it might be nice to have a default vanilla stack descriptor file available with the command, or some kind of separate command that will give users a template. I understand that within the project we will largely be using this with our own stack descriptor files, but for the sake of ease of use for users that might want to leverage this tool themselves we should make it as easy as possible.

[sophiewigmore]

Also, unrelated and probably not a big deal but I observed the packing process taking substantially longer now:

 ‣ time ./scripts/package.sh -v 1.2.3
real    0m40.948s
user    3m42.375s
sys     0m28.846s

This is versus the user 0m7.399s for the version on main. Just wanted to point this out and make sure this is expected.

[ryanmoran]

Also, unrelated and probably not a big deal but I observed the packing process taking substantially longer now:

 ‣ time ./scripts/package.sh -v 1.2.3
real    0m40.948s
user    3m42.375s
sys     0m28.846s

This is versus the user 0m7.399s for the version on main. Just wanted to point this out and make sure this is expected.

I'm not seeing this same slowdown. Can you confirm that this happens consistently with rebuilds? Is this from a fresh clone of the repo?

[ryanmoran]

I have a small suggestion I want to hear your opinion on. I think that it might be nice to have a default vanilla stack descriptor file available with the command, or some kind of separate command that will give users a template. I understand that within the project we will largely be using this with our own stack descriptor files, but for the sake of ease of use for users that might want to leverage this tool themselves we should make it as easy as possible.

This sounds reasonable, but maybe requires a separate issue and PR?

[sophiewigmore]

I'm not seeing this same slowdown. Can you confirm that this happens consistently with rebuilds? Is this from a fresh clone of the repo?

It was a fresh clone of the repository, yes. But you're right subsequent builds are 11 seconds (when the build directory is removed before) which is much more reasonable!

[sophiewigmore]

@ryanmoran issue filed for my suggestion: #56

[sophiewigmore]

@ryanmoran Appreciate the documentation additions. Can you fix the merge conflicts? Then we can get this merged in!