Add Contract Management integration tests with role-based access scenarios

[Copilot]

Implements integration test suite for Contract Management covering Admin, Estate, and Viewer roles with assertions against hardcoded test data.

Test Structure

• ContractManagement.feature: 20 Reqnroll scenarios

  • Admin (2): Access denial verification
  • Estate (12): Full CRUD operations including product and transaction fee management
  • Viewer (6): Read-only access with permission boundary validation

• ContractManagementPageHelper.cs: Playwright automation layer

  • Navigation, verification, and interaction methods
  • Shouldly assertions against stubbed data (Standard Transaction Contract, Safaricom operator, Mobile Topup products)
  • Proper wait mechanisms using WaitForLoadStateAsync() and element-specific waits

• ContractManagementSteps.cs: Step definitions bridging feature file to page helper

Example Scenario

@ContractManagement @EstateRole
Scenario: Estate user can add a product to contract
    Given the user is authenticated as an "Estate" user
    When the user navigates to the Edit Contract page for the first contract
    And the user clicks on the "Add Product" button
    Then the Add Product modal is displayed
    When the user enters "New Product" in the product name field
    And the user enters "100" in the value field
    And the user clicks on the "Add Product" button in the modal
    Then the product is added successfully

Implementation Notes

• Follows existing test patterns (Dashboard, EstateManagement, MerchantManagement)
• Uses hardcoded test contract ID 44444444-4444-4444-4444-444444444444 from StubbedMediatorService
• Application startup configuration required separately (not included per requirements)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Contract Management Integration Tests</issue_title>
<issue_description>I want a suite of integration tests built for the Blazor Server Application.

This set of tests will be for the Contract Management.

Can you build the tests based on the functionality available in terms of user roles (Admin/Estate/Viewer), I want these tests to have assertions based on the hard coded test data that's in the application (this can be swapped out at a later date)

I would like tests to cover all the functionality areas including any screens that add/edit/remove.

Any assertions will be done with the Shouldly framework.

I must stress that the only code I am expecting from this is:

A reqnroll feature file
A hooks file to allow control of the browser application (based on playwright)
A file with steps to control the browser application
A file that links the feature file to the application steps code

I will deal with how the application actually gets started up for the testing at a later point</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Contract Management Integration Tests #585

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.