Create GitHub actions to test new code before merging

### Background on the problem the feature will solve/improved user experience
Add GitHub Actions to test and build new code pushed to a branch or committed to a pull request. Code that passes all the steps in the GitHub action can be merged in the repository.

Prerequisite: This should be installed after we start adding python code to this repo.

### Describe the solution you'd like
A GitHub action runs whenever code is committed to any branch or PR is made to the main branch.

Each action will
- [ ] install dependencies
- [ ] build for production
- [ ] run all tests
- [ ] linting, we haven't chosen a linter so let's discuss options in the comments

### Tasks
- [ ] Ensure install, build and lint steps run locally on your system
- [ ] Read more about [GitHub actions](https://docs.github.com/en/actions/learn-github-actions), in the Build and Test section
- [ ] Create GitHub actions for each folder described above. You can read more [Python build actions here](https://docs.github.com/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python?langId=py).
- [ ] Commit and push your GitHub action code.
- [ ] Go to the [Actions tab](https://github.com/Call-for-Code-for-Racial-Justice/TakeTwo-DataScience/actions) to see if it worked.

### Acceptance Criteria
- GitHub action runs for every new code commit and PR.

FYI @upkarlidder

Inizia dalla documentazione collegata di GitHub Actions e dalla guida Python build-actions, quindi ispeziona il repository per determinare i relativi comandi di installazione, build, test e linting; l’issue non indica file o test specifici. Il lavoro è completato quando Actions viene eseguito per i nuovi commit e le pull request e completa i passaggi concordati di installazione, production build, test e linting.

Scritto dal modello di indicizzazione a partire dal testo della issue.