Issue:
Bug: [CYPRESS]: Verify Time Range Filters in "Payment operations" page.



---

### **Title**: Verify Time Range Filters in "Payment operations" page.

---

### **Description**:

This task is to write and execute automated test cases for various UI elements and functionalities on the "Payment Operations" page. The tests should validate that key UI elements are present and that core functionalities operate as expected.

### **Objective**:

Ensure that the "Payment Operations" page displays all key elements and that interactions like searching, filtering, and report generation work as intended. The task will include multiple test cases covering these areas.

### **Pre-requisites:**

[Create a dummy connector](https://github.com/juspay/hyperswitch/issues/6125)
[Use the SDK to process a payment](https://github.com/juspay/hyperswitch/issues/6124)

---

### **Test Cases**:

#### **Test Case 1: Verify Time Range Filters**

- **Pre-requisites**: Make a payment.
- **Steps**:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Verify the default time range is "Last 30 Days."
  4. Click on the time range dropdown and select various options: "Last 30 Mins," "Last 1 Hour," "Last 2 Hours," etc.
- **Expected Results**:
  - For each selected time range, verify the payments are displayed accordingly.
  - "Customize columns" button visibility should be checked based on the presence of payments.

#### **Test Case 2: Verify "Custom Range" in Time Range Filters**

- **Pre-requisites**: Make a payment.
- **Steps**:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Select "Custom Range" in the time range dropdown.
  4. Select a custom date range and click "Apply."
- **Expected Results**:
  - Payments within the selected range should be displayed.
  - The selected time range should be displayed when the dropdown is minimized.

---

### **Acceptance Criteria**:

1. All test cases should pass with the expected results.
2. Each test case must verify the required functionality or UI element.
3. The tests should be included in the regression suite and executed in the CI/CD pipeline.

---

### **Submission Process**:
- Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
- Once assigned, submit a pull request (PR).
- Maintainers will review and provide feedback, if any. 
- Maintainers can unassign issues due to inactivity, [read more here](https://github.com/juspay/hyperswitch/wiki/Hacktoberfest-Contribution-Rules).
- For this issue, please submit a PR on juspay/hyperswitch-control-center repo, and link it to the issue.

Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.

---

Pull request description:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->
This PR updates the schedule for the auto release workflow to run every Tuesday, Wednesday and Thursday.

## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless its an obvious bug or documentation fix
that will have little conversation).
-->
We mostly won't be making any releases on Mondays and Fridays, so yeah.

## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
N/A

## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [x] I reviewed submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable


Testing:

N/A

Patch: