Fix GitHub ACtions pipeline: ensure Cypress component tests run correctly

[Keikonichi]

Description

The following adjustments were made:

• Fixed the syntax of the step responsible for running component tests.
• Ensured that the cypress-run job includes both E2E and component tests.
• Adjustments to make sure the workflow is correctly identified and all tests are executed.

This change ensures that the CI/CD pipeline continues to function properly and that component tests are executed as expected.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Testing

Steps to validate the tests:

1. Ran the component tests locally using:

yarn cypress run --component

2. Verified that all tests passed without errors.
3. Pushed the changes to GitHub and monitored the execution in GitHub Actions.
4. Confirmed that the cypress-run job successfully executed the component tests.

Developer Checklist

General

• Code is appropriately commented, particularly in hard-to-understand areas
• Repository documentation has been updated (Readme.md) with additional steps required for a local environment setup.
• No console.log or related logging is added.
• No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).
• Documented with TSDoc all library and controller new functions

Tests

• All existing unit and end to end tests pass across all services

Merge Request Review Checklist

• High risk and core workflows have been tested and verified in a local environment.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud