Bug: [feat] show error code and message in cypress reports



show error code and message in cypress reports.

this is helpful to debug failures in ci
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->

This PR introduces error code and error message validations.  
This nullifies the need to re-run the ci check manually in local every the check just to see the reason for the failure.
With that, `error_code` and `error_message` will now be printed in the ui in every run and hence, this makes the generated reports more reliable.

### 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 it is an obvious bug or documentation fix
that will have little conversation).
-->

i want reports to serve a purpose and reliable.

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

when a ci check fail, especially from the connectors' end, ci takes a screenshot of the ui, as usual, but that will now contain the error code and message.

since adyen yet again got into some issues with save card flow, it is possible to test my changes directly without the need to make any modifications to the test:

<img width="539" alt="image" src="https://github.com/user-attachments/assets/c2037bb2-b393-410d-b5b4-feb093a94a7a" />


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

- [x] I formatted the code `prettier . --write`
- [ ] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
