Starter Kit: CI/CD with Github Actions

### Background on the problem the feature will solve/improved user experience
Manual cloud deployments are tedious.

### Describe the solution you'd like
Once we've validated our manual deployments we would like to have CI/CD to deploy easily to cloud.

### Tasks
For all TakeTwo repositories:
- [ ] https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo
- [ ] https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo-Marker-ChromeExtension
- [ ] https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo-DataScience/
- [ ] https://github.com/Call-for-Code-for-Racial-Justice/taketwo-webapi/

Add github actions for:
- [ ] building
- [ ] unit testing
- [ ] accessibility testing
- [ ] Refer to [chrome extension accessibility documentation](https://developer.chrome.com/docs/extensions/mv2/a11y/)
- [ ] linting
- [ ] deployment (contact @upkarlidder for access)
- [ ] Deploy to Code-Engine as an application
- [ ] Deploy to IBM Kubernetes Services (IKS)

Related Issues:
- https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo-WebAPI/issues/7
- https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo-Marker-ChromeExtension/issues/23

### Acceptance Criteria

Start by reviewing the TakeTwo, TakeTwo-Marker-ChromeExtension, TakeTwo-DataScience, and taketwo-webapi repositories, along with related issues 7 and 23. Map the requested GitHub Actions for building, unit testing, accessibility testing, linting, and deployment to Code Engine and IKS; done requires coverage of all four repositories and the listed deployment targets.

Written by the indexing model from the issue text.