Handle nonsensical signal min/max bounds

```
 SG_ ByteWithNegativeMin : 32|8@1+ (1,-2) [-127|127] "" Vector__XXX
```
^ In this signal, the min bound of `-127` is lower than the lowest representable value `-2`.
If one were to pass in a value lower than `-2` to the setter function, it would underflow and result in nonsense.
`check_ranges` doesn't help either as it only validates that the value is within `-127..=127`