fix: add CodeQL workflow with disk space cleanup

[tristandubbeld]

Summary

This PR adds a CodeQL workflow with disk space cleanup to prevent "No space left on device" errors during analysis.

Changes

• Added .github/workflows/codeql.yml - CodeQL workflow with disk space cleanup step
• Added .github/codeql/codeql-config.yml - CodeQL configuration to exclude unnecessary files from analysis

Verifying the Workflow

• The workflow will automatically trigger on:
  • Pushes to main branch
  • Pull requests to main branch
  • Weekly schedule (Sundays at midnight UTC)
• You can check the Actions tab to see workflow runs

What Should Be Disabled

• Disable the "Default setup" for CodeQL analysis:
  • In Settings → Code security and analysis → Tools → CodeQL analysis
  • Click the three-dot menu (⋯) next to "Default setup"
  • Select "Disable CodeQL" or "Switch to advanced setup"
  • This prevents conflicts with the custom workflow file

How It Works

1. Disk Space Cleanup: The workflow starts by removing unnecessary tools and caches (~5-10 GB freed)
2. Path Exclusions: The CodeQL config excludes node_modules, build artifacts, test fixtures, and other non-production files
3. Analysis: CodeQL analyzes only production JavaScript/TypeScript code

This should resolve the disk space issues seen in previous CodeQL runs and the "Code scanning configuration error" currently showing in the UI.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

• Application (fast + production)
• Application (fast + stream)

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.