CI: Optimize CI workflow to run tests and linting only on relevant file changes

[drikusroor]

The PR involves significant restructuring of the GitHub Actions workflows, splitting the original CI workflow into separate workflows for backend and frontend, and updating conditions for running certain actions. Additionally, minor changes are made to the Storybook workflow and a frontend component.

Changes in Workflows

1. Rename and Modify Backend Workflow

• File renamed: .github/workflows/ci.yml to .github/workflows/ci-backend.yml
• New Name: Backend Test & Lint
• Trigger Conditions Updated:
  • Runs on push and pull_request events, but only if changes are made in the backend/** directory.
• Removed Jobs: All frontend-related jobs have been removed from this workflow.

2. Create Separate Frontend Workflow

• New File: .github/workflows/ci-frontend.yml

• Name: Frontend Test & Lint

• Trigger Conditions:

  • Runs on push and pull_request events, but only if changes are made in the frontend/** and the .yarn directory.

• Jobs Added:

  • frontend-test: Runs frontend tests using Docker.
  • frontend-coverage-badge: Generates a frontend coverage badge and pushes it to a separate branch if on the develop branch.
  • frontend-lint: Lints frontend code using Docker.

3. Update Storybook Workflow

• File Modified: .github/workflows/storybook.yml
• Trigger Conditions Updated:
• Runs on push and pull_request events for changes in the following paths:
  • frontend/**
  • .github/workflows/storybook.yml
  • .yarn/**
  • .storybook/**

Summary

• Backend Workflow: Now exclusively handles backend tests and linting, triggered by changes in the backend directory.
• Frontend Workflow: Introduced to handle frontend tests, coverage generation, and linting, triggered by changes in the frontend directory.
• Storybook Workflow: Updated to be triggered by changes in specific frontend-related paths.
• Code Change: Minor formatting change in the frontend App component to remove trailing whitespace.