Currently if you pass decimal values to rgb or bgRgb, it will generate output with those decimals, which iTerm silently ignores.
Not sure if this is the ideal fix, since when rgb values are from 0-255 it's *commonly* assumed that they're integers. Maybe chalk should just throw an error instead. But this is a bug I came across when converting from 0-1 r,g,b, which is common, so there should be at least some indication.
