Create a CI pipeline

[rahearn]

The full eventual pipeline will require:

• unit tests (Create a Github Actions pipeline that runs tests #35)
• a11y scan (Run a11y scans on code push #37)
• dynamic security scan #46
• static security scan #39
• Run dependency audits on CI #44
• deployment to a staging environment
• deployment to production (maybe not until in a fully-moderate environment)

Break each piece into its own task to implement

[rahearn]

Use Github Actions for this, at least at first.

[rahearn]

@hartsick thoughts on adding a ruby style enforcer? I'm a fan of https://github.com/testdouble/standard (which is basically rubocop with Opinions)

[hartsick]

@rahearn I'm not the biggest style enforcer fan (feel it's often more burden than worth on small teams, and consistency and readability can sometimes be a tradeoff) but don't feel strongly about it! if you have a strong preference go for it

[rahearn]

if you have a strong preference go for it

I'm fine with tabling it until we have an issue with bikeshedding