Enabling NO_HZ_IDLE may cause large timeout values to be sent to the
host tick emulation handler implemented by the client domain.

Since we refrain from converting the timeout value to timer ticks but
keep it as a count of nanoseconds for stolen timers, we have to make
sure that such value will still fit in the ->set_next_event()
(unsigned long) argument without overflowing.

Cap the maximum delay value which may be passed to ->set_next_event()
by setting max_delta_ns appropriately in the clockevent definition of
stolen timers.