[GitHub] Add path filters to avoid unnecessarily re-running tests

[SirzBenjie]

What are the changes the user will see?

N/A

Why am I making these changes?

Part of the test refactor (sort of). We do not need to re-run tests in commits that only change files that cannot impact tests (e.g. the README file). These tests are long running.

What are the changes from a developer perspective?

In summary, the test github action will only re-run when source code files, test files, any file that can impact the build, or the test workflow file itself has changes.

Accomplished by added the following paths filter to .github/workflows/tests.yml

paths:
      # src and test files
      - "src/**"
      - "test/**"
      - "public/**" # PLEASE REVIEW -- Does it make sense to include this? Can modifying these break tests? (REMOVE COMMENT AFTER REVIEW)
      # Workflows that can impact tests
      - ".github/workflows/test*.yml"
      # top-level files
      - "package*.json"
      - ".nvrmc" # Updates to node version can break tests
      - "vite.*.ts" # vite.config.ts, vite.vitest.config.ts, vitest.workspace.ts
      - "tsconfig*.json" # tsconfig.json tweaking can impact compilation
      - "global.d.ts" # I think this can impact tests? (REMOVE COMMENT AFTER REVIEW)
      - ".env.*" # PLEASE REVIEW -- can these impact test behavior?
      # Blanket negations for files that cannot impact tests
      - "!**/*.py" # No .py files
      - "!**/*.sh" # No .sh files
      - "!**/*.md" # No .md files
      - "!**/.git*" # .gitkeep and family

Screenshots/Videos

N/A

How to test the changes?

You'd have to make a commit and open a pull request that only changes a file, like README.md, to verify that the tests aren't automatically re-run. The, make a commit and open a pull request that changes any source code file and verify tests are still re-run.

Checklist

• I'm using beta as my base branch
• There is no overlap with another PR?
• The PR is self-contained and cannot be split into smaller PRs?
• Have I provided a clear explanation of the changes?
• [ ] Have I tested the changes manually?
• [ ] Are all unit tests still passing? (npm run test)
  • [ ] Have I created new automated tests (npm run create-test) or updated existing tests related to the PR's changes?
• [ ] Have I provided screenshots/videos of the changes (if applicable)?
  • [ ] Have I made sure that any UI change works for both UI themes (default and legacy)?