ci: running tests in BrowserStack not working

[SuperITMan]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/NationalBankBelgium/stark/blob/master/CONTRIBUTING.md#got-a-question-or-problem

Current behavior

In the CI, tests executed in BrowserStack never finish.

16:31:12] I/testLogger - 

[16:31:12] I/launcher - 0 instance(s) of WebDriver still running
[16:31:12] I/launcher - Safari #61 failed with exit code: 1
[16:31:12] I/launcher - Chrome #71 failed with exit code: 1
[16:31:12] I/launcher - Chrome #21 passed
[16:31:12] I/launcher - Safari #41 passed
[16:31:12] I/launcher - IE #01 passed
[16:31:12] I/launcher - Edge #11 passed
[16:31:12] I/launcher - Firefox #31 passed
[16:31:12] I/launcher - Safari #51 passed
[16:31:12] I/launcher - overall: 2 process(es) failed to complete
[16:31:12] E/launcher - Process exited with error code 100
Error: Process completed with exit code 100.

Expected behavior

Tests in BrowserStack should be working.

Minimal reproduction of the problem with instructions

See tests results: https://github.com/NationalBankBelgium/stark/actions/runs/7476972968/job/20348590445, https://github.com/NationalBankBelgium/stark/actions/runs/7474133876/job/20339657372

What is the motivation / use case for changing the behavior?

Having working E2E tests in Stark.