chore(ci): remove semgrep workflow

[rhamzeh]

This PR removes the .github/workflows/semgrep.yaml file, as we will no longer have access to semgrep..

Summary by CodeRabbit

• Chores
  • Removed an internal CI workflow related to static analysis.
  • Streamlines automation pipeline and reduces maintenance overhead.
  • No impact on user-facing features or behavior.

[coderabbitai]

Walkthrough

Removed the GitHub Actions workflow for Semgrep CI by deleting .github/workflows/semgrep.yaml, which previously ran Semgrep on pushes to the main branch.

Changes

Cohort / File(s)	Summary of Changes
CI Workflow Removal .github/workflows/semgrep.yaml	Deleted Semgrep CI workflow that ran on pushes to main, using returntocorp/semgrep container, checkout step, and semgrep ci execution with SEMGREP_APP_TOKEN.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fadd174 and 22339ad.

📒 Files selected for processing (1)

• .github/workflows/semgrep.yaml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/semgrep.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build-and-test-java-sdk
• GitHub Check: build-and-test-go-sdk

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/remove-semgrep-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Siddhant-K-code]

LGTM ✅

Tests are failing due to spellchecks, which should be fine after the merge of #575.