Improve runtime validation of packet properties

[mkapal]

Some packet properties are validated at runtime and throw a RangeError if the provided value is not within range for LFS.

Instead of throwing errors, the values could be clamped, trimmed or packet not being sent at all depending on the use case.

Examples:

• IS_BTN - ClickID, T, L, W, H
• IS_MSX, IS_MSL, IS_MST - Msg, Text

Each property type (byte, double...) could have its own validation of the allowed range.