Reduce defaultCommandTimeout configuration for E2E tests

[cnotv]

Description

As temporary solution, last year we increased the defaultCommandTimeout of the waiting response for the E2E tests, giving the chance to solve the cause of the delay.
The vast majority of the errors are although covered in a very shorter time, still keeps the whole process too long.

Reduce timeout to default (2s) or a similar value, instead of current (60s).

To be solved after #9040

[cnotv]

Although in case of errors it avoids to wait between 2 to 3 times the normal time, overall it does not seems to reduce so much on an average of many errors:

• defaultCommandTimeout 4s, with a lot of errors (CI, dashboard)
  • admin: 59m 18s
  • user: 14m 43s
• Current defaultCommandTimeout 1min, only 1 flaky case which is kinda best scenario (CI, dashboard)
  • admin 1h 5m 46s
  • user 24m 46s

Branch comparison: master...cnotv:dashboard:feature/8956-reduce-e2e-timeout

PS: For this scenario have been reduced/removed requestTimeout, wait() commands and defaultCommandTimeout.

[cnotv]

In another attempt I tried to remove any fixed waiting time I crossed, although it did not produce very huge improvements as well:

• CI, Dashboard
• admin 51m 16s
• user 13m 47s

Given these circumstances, we may want to simply tackle down flaky tests issues and handle performances issues (mainly API responses).

We could reduce safely this timeout afterwards just for the flaky/errors sake.
#9233 needs to be completed before start this task then.