Add python and eslint automations to CI/CD pipeline

### Dependency

- [ ] #609 - we should resolve all eslint errors first, otherwise no one will be able to merge or deploy anything.

### Overview

As a developer, we should add linter scripts to the CI/CD pipelines via github actions, so that our codebase will always remain clean and maintainable.

Notes
- The current github action needs updating - it can be found in `/.github/workflows/linter.yml`

### Action Items

- [ ] Make a github action to check code is linted before merging to `develop`
- [ ] Make a github action to check code is linted before merging to `main`
- [ ] The gihub action should be migrated to v4

### Resources/Instructions

[Resources](https://hackforla.github.io/CivicTechJobs/resources/)

- https://hackforla.github.io/CivicTechJobs/developer/frontend/#linting