test: fix e2e compatiblity tests for provider v4.3.0-lsm

[bermuell]

Description

Issue: e2e compatiblity tests are failing with provider version v4.3.0-lsm

Reason:
since v4.3.0-lsm provider supports expedited governance proposal
which requires to set related parameter in genesis file.
current compatibility tests failed not setting this parameter with a valid value.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• Included the correct type prefix in the PR title
• Targeted the correct branch (see PR Targeting)
• Provided a link to the relevant issue or specification
• Reviewed "Files changed" and left comments if necessary
• Confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• Confirmed the correct type prefix in the PR title
• Confirmed all author checklist items have been addressed
• Confirmed that this PR does not change production code

Summary by CodeRabbit

• Chores
  • Updated nightly end-to-end tests to include version changes for provider and consumer configurations.

[coderabbitai]

Walkthrough

Walkthrough

The recent changes revolve around two core areas: enhancing version management and configuration handling. The .github/workflows/nightly-e2e.yml file now updates the go run command for the compatibility-test job to handle specific version changes for providers and consumers. In tandem, the config.go file introduces new handling logic for versions v4.3.0-lsm and above, integrating special parameters for governance proposals and slashing functionality.

Changes

File	Change Summary
.github/workflows/nightly-e2e.yml	Updated the go run command within the compatibility-test job to include version changes for both provider and consumer versions.
tests/e2e/config.go	Enhanced logic in CompatibilityTestConfig function to handle configurations for versions >= v4.3.0-lsm, adding governance proposals and slashing functionality.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Workflow
    participant Config
    participant Tests

    User->>Workflow: Trigger nightly-e2e.yml
    Workflow->>Tests: Run compatibility-test with updated versions
    Tests->>Config: Invoke CompatibilityTestConfig with provider and consumer versions
    Config->>Tests: Return updated TestConfig for versions >= v4.3.0-lsm
    Tests->>Workflow: Execute tests with new parameters
    Workflow->>User: Return test results

Loading

---

Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 395524a and f9e2aca.

Files selected for processing (1)

• .github/workflows/nightly-e2e.yml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/nightly-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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

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.