This adds a CircleCI config file based on the same config I use for my own website. It makes it easy
to have multiple steps running in parallel, such as running tests and coverage reports.

Forcing contributors to use Commitizen to format their commit messages will make our lives much
simpler, especially once we've added `semantic-release`.

Add `semantic-release` to the repo and the build pipeline. This will handle automatically publishing
to npm based on commit messages.

#13

The Roll For Guild Node container doesn't include `git`, which is required by semantic-release.

#13

I got a bunch of permission errors last time I tried to build in ~/app. I'm pretty sure building in
the default directory should work just as well.

I've removed containers from tthe config entirely because I don't think we need them. Hopefully this
will fix the build. 🤷🏻‍♂️

Switching back to container because I have no idea how to fix the errors that came up without them.
Additionally, I'm changing the working directory to `~/tmp` to see if that works better than the
`~/app` folder.

I think the issue was that the app was being built into the root user's home directory rather than
the `circleci` user's home directory. 🤞

I finally figured it out. Restoring the cache was trying to restore the cache from an older build
that used a different image in which the root user was the one doing all the tasks. I'm pushing a
build that doesn't restore the cache, then I'll add those steps back in after the next build.

By removing strict host key checking for Github, we shouldn't run into the issue where host
authenticity verification stalls the deployment.

Repository cloning in the deploy step was 100% unnecessary.

Add `commitlint` to enforce proper formatting for all commit messages

#13

I've updated the `package.json` so it points back at @BcRikko's repo instead of mine.

#13