Prevent overflow when using gettimetick(0)

[Kenpachi2k13]

Pull Request Prelude

• I have followed proper Hercules code styling.
• I have read and understood the contribution guidelines before making this PR.
• I am aware that this PR may be closed if the above-mentioned criteria are not fulfilled.

Changes Proposed

Prevent overflow of script variables (signed integer) when using gettimetick(0) by doing a bitwise AND operation on timer->gettick()' and INT_MAX.
This decreases the tick loop interval from ~50 to ~25 days, but I think this is the best approach to fix this issue.

Issues addressed: #2779

[Lemongrass3110]

This will still lead to wrong condition checks for many user scripts that do checks based on ticks for time difference.

[Kenpachi2k13]

@Lemongrass3110

This will still lead to wrong condition checks for many user scripts that do checks based on ticks for time difference.

gettimetick(0) is supposed to be used where one needs to precisely validate a short lapse of time.
So the only problem I can imagine is accidentally having the loop interval being reset between setting the start tick and setting the end tick.
If there's something I don't consider, please tell me or provide an example case. 😊