Bug 1852108

Description of problem:

Sanlock has complex timeouts based on I/O timeout (default 10 seconds) used
to renew delta leases and check host liveliness. These operations cannot
use arbitrary timeout or user configurable timeout.

The timeouts are documented here:
https://pagure.io/sanlock/blob/master/f/src/timeouts.h

Sanlock reuse the same base timeout (10 secodns) for other storage operations 
like formatting lockspace area, formatting resource area, creating rindex.
These operations can use arbitrary timeout or user configurable timeout.

A single timeout when renewing a lease is not critical, since the operation
is retried in the next check interval.

Single timeout when creating a lockspace or reosource fail the operation in
the management system using sanlock.

In oVirt system tests, running on virtualized environment, with unpredictable
load, we experience too much failures in sanlock operations that could be 
avoided if we had larger timeout.

Use separate timeout for normal storage operations, with larger default value
so these operations are less likely to fail on overloaded environments.

Make the new timeout configurable so users can adapt the timeout as needed.