*Context:
With OPT-4069 we had a bug that the incorrect unit was used for the scroll timeout since it wasn't clear from its name in which unit the configuration property is in. During the review it came up that there are at least two more constants which could potentially lead to a similar bug:

• es.connection.timeout and
• engine-commons.connection.timeout

AT:

• for all time configuration properties it's clear from their name which unit they are in
• at least the configurations es.connection.timeout and engine-commons.connection.timeout are adjusted
• the configuration section in the technical docs is adjusted accordingly