`Duration` support for time based utils and helper

[martingrossmann]

Is your feature request related to a problem? Please describe.
There are some utils and helper classes which can be controlled via one or more time parameters:

• CONTROL.retryFor/withTimeout
• TimerUtils
• WEB_DRIVER_MANAGER.keepAlive https://docs.testerra.io/testerra/stable/index.html#_keep_a_session_alive
• Optional page (waitForPage): https://docs.testerra.io/testerra/stable/index.html#_optional_pages

The time value is given as int, wich represents seconds or milli seconds. That can be confusing and be a cause of wrong using of that classes/methods.

Describe the solution you'd like
Add Java Duration support and mark current implementations as deprecated.

[mreiche]

• Duration is flexible, but IMHO too technically. I would prefer writing waitFor(0.3) instead of waitFor(Duration.ofMillis(300)). I explicitly decided against Duration because of that.
• Duration supports a lot of time features you may not need in test context. ea. ofNanos(), ofHours(), ofDays()
• I would support Duration as method overloading, but do not mark the current easy readable implementations as @deprecated

[martingrossmann]

Selenium 4 expectes for all timeout and waiter methods Duration. The usage with int and a TimeUnit is deprecated:
https://www.selenium.dev/documentation/webdriver/getting_started/upgrade_to_selenium_4/#waits-and-timeout

I prefer to do the same with Testerra after releasing Testerra 2.4 with Selenium 4