ci: remove v2 migration test from scheduled CI and release workflow

[lumtis]

Description

The test is not functional when running from develop as it uses v2 contracts pre-deployed by default
 
Just keep it in manual workflow for now for exceptional case (we have to make a new hotfix on v20)

Will be completely removed once v2 migration completed

Summary by CodeRabbit

• Chores
  • Updated test execution logic to streamline conditions for running specific tests based on GitHub event types.
  • Removed certain outputs for push and schedule events, focusing on workflow_dispatch events for V2_MIGRATION_TESTS.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in the .github/workflows/e2e.yml file focus on modifying the logic for determining which tests to execute based on various GitHub event contexts. The setting of the V2_MIGRATION_TESTS output has been refined to only apply to workflow_dispatch events, while it is omitted for push events targeting release/* branches and schedule events. The overall structure and job dependencies of the workflow remain unchanged, ensuring that the matrix configuration continues to utilize outputs from the matrix-conditionals job.

Changes

File	Change Summary
.github/workflows/e2e.yml	Updated matrix-conditionals job logic to set V2_MIGRATION_TESTS only for workflow_dispatch events; removed settings for push and schedule events.

Possibly related PRs

• fix!: tolerate v2 contracts in tss migration tests #3002: This PR involves changes to the e2e tests, specifically addressing issues related to the V2 contracts in the TSS migration tests, which may interact with the test execution logic modified in the main PR's workflow file.
• fix: fix admin e2e tests and bump protocol contracts #3006: This PR also focuses on fixing admin end-to-end tests, which are likely to be affected by the changes in the .github/workflows/e2e.yml file regarding how tests are triggered based on event contexts.

Suggested labels

ci, no-changelog

Suggested reviewers

• skosito
• gartnera
• fbac
• kingpinXD
• ws4charlie

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 250b90e and 53f526d.

📒 Files selected for processing (1)

• .github/workflows/e2e.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/e2e.yml

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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.

Documentation and Community

• 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.