kernel/timeout: Clamp ticks argument to lower bound
kernel/timeout: Clamp ticks argument to lower bound

Our funny convention holds that passing ticks==1 to _add_timeout()
means "at the next tick".  But that means that 1, 0, and all negative
numbers are expected to behave the same.  In ticked mode, that's fine
because it will, after all, expire at the next tick.

But in tickless, the next announcement may be for several ticks, and
that zero will appear to expire "before" the next tick in the
consumption loop.

Make sure all "next tick" expirations look the same.

Signed-off-by: Andy Ross <c70f9a6bf6ee0cd69c8af4ce5e6b131945769315@intel.com>

finikorg/zephyr,Vudentz/zephyr,punitvara/zephyr,punitvara/zephyr,zephyrproject-rtos/zephyr,Vudentz/zephyr,zephyrproject-rtos/zephyr,Vudentz/zephyr,ldts/zephyr,punitvara/zephyr,zephyrproject-rtos/zephyr,explora26/zephyr,finikorg/zephyr,explora26/zephyr,nashif/zephyr,GiulianoFranchetto/zephyr,ldts/zephyr,nashif/zephyr,galak/zephyr,galak/zephyr,galak/zephyr,GiulianoFranchetto/zephyr,Vudentz/zephyr,explora26/zephyr,nashif/zephyr,explora26/zephyr,finikorg/zephyr,punitvara/zephyr,finikorg/zephyr,zephyrproject-rtos/zephyr,nashif/zephyr,finikorg/zephyr,zephyrproject-rtos/zephyr,GiulianoFranchetto/zephyr,explora26/zephyr,ldts/zephyr,GiulianoFranchetto/zephyr,nashif/zephyr,punitvara/zephyr,ldts/zephyr,galak/zephyr,galak/zephyr,GiulianoFranchetto/zephyr,Vudentz/zephyr,Vudentz/zephyr,ldts/zephyr