Bug: [CYPRESS]: Verify Columns in "Payment operations" page.



---

### **Title**: Verify Columns 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: Customize Columns in Payments Table**

- **Pre-requisites**: Make a payment.
- **Steps**:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Click on the "Customize Columns" button.
  4. Verify that the following column names are present:
     - Merchant Order Reference Id
     - Metadata
     - Payment Status
     - Payment Method Type
     - Payment Method
     - Payment ID
     - Customer Email
     - Description
     - Created
     - Connector Transaction ID
     - Connector
     - Amount
     - AmountCapturable
     - Authentication Type
     - Profile Id
     - Capture Method
     - Client Secret
     - Currency
     - Customer ID
     - Merchant ID
     - Setup Future Usage
     - Attempt count
  5. Select all columns.
  6. Click on "22 Columns selected."
  7. Click on the "Customize Columns" button.
  8. Unselect all optional columns: 
     - AmountCapturable
     - Authentication Type
     - Profile Id
     - Capture Method
     - Client Secret
     - Currency
     - Customer ID
     - Merchant ID
     - Setup Future Usage
     - Attempt count
  9. Click on "12 Columns selected."
- **Expected Results**:
  - All selected columns should be present and visible in the payments table.
  - Only the selected columns should be visible after unselecting optional columns.

#### **Test Case 2: Search Columns in "Customize Columns" List**

- **Pre-requisites**: User is logged in.
- **Steps**:
  1. Navigate to the "Payment Operations" page.
  2. Click on the "Customize Columns" button.
  3. Verify that the search bar has the placeholder "Search in 22 options."
  4. Search for any available column names such as "Merchant," "Profile," "Payments."
- **Expected Results**:
  - Resulting column names should contain the search string.

#### **Test Case 3: Search Invalid Columns in "Customize Columns" List**

- **Pre-requisites**: User is logged in.
- **Steps**:
  1. Navigate to the "Payment Operations" page.
  2. Click on the "Customize Columns" button.
  3. Verify that the search bar has the placeholder "Search in 22 options."
  4. Search for invalid column names such as "abacd," "something," "createdAt."
- **Expected Results**:
  - "No matching records found" text should be shown.
  - Clicking on the "X" button should clear the search text and display all column names.

---

### **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, submit a PR on https://github.com/juspay/hyperswitch-control-center repo, and link to the issue.

Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.

---
## 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 -->
- Also push to public docker repositories for all release tags

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## 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).
-->


## 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)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [ ] I reviewed submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable
