Set up workflow for publishing component-library to npm

[jaronheard]

As a follow-up to #398, we need to figure out our publishing workflow for publishing the component-library to npm. There are a few other utility packages that should be published to npm as well.

This is a usage where lerna is useful.

[jaronheard]

Here's my plan for publishing:

Which packages will be published?

• We can set all the packages that we don't want to publish to 'private'
  My proposal: set all project and year packages to private

When and how will projects get published?
Packages will be published semi-regularly (not automatically) using semantic versioning

Who will have publishing permissions?
Me, for now, expand to others as necessary

[jaronheard]

After digging into this a little bit, I've revised my thinking on publishing

When and how will projects get published?
Canary versions published automatically from master branch using CI tooling
Release versions of packages will be published manually semi-regularly (not automatically) using semantic versioning

[jaronheard]

This is working now! 3.0.0 has been published, and we're now publishing canary versions with the CI tag.