Add separate CONST_OVERLAY_NEXT_TIME_BLOCK to use CONST_OVERLAY_TADO_MODE for the actual TADO_MODE

[deichcode]

In the const.py there is no overlay type/mode constant that is set to "TADO_MODE". However, this string is supported by the tado API, and if used as typeSkillBasedApp the overlay will remain until either the next time block is reached or the home state is changed.

At the moment the CONST_OVERLAY_TADO_MODE is set to "NEXT_TIME_BLOK". In contrast to the actual "TADO_MODE," this overlay remains until the time of the next time block arrives independently of the home state.

The two different types are reflected in the UI like this

TADO_MODE

NEXT_TIME_BLOCK

Therefore, I'd suggest that CONST_OVERLAY_TADO_MODE is now set to "TADO_MODE" and a new CONST_OVERLAY_NEXT_TIME_BLOCK is introduced. Since this is a breaking change for everyone using the previous definition of CONST_OVERLAY_TADO_MODE, it should be discussed how to proceed. However, using a const named this way might have caused unintended behavior in the past.

[wmalgadey]

This will change the default behavior of tado in homeassistant, wouldn't it? I don't know, if it is a dealbreaker to change it to the next time block or until the next home/away change!?