Fix set_price float coercion causing silent Booking.com API failure
set_price on both clients accepted floats despite an int signature.
_BookingClient.set_price serialized via str(price), turning 132.0 into
"132.0" — a string Booking's inventory API silently discards, leaving
the price null on the next calendar read. _AirbnbClient passed the
float directly as a JSON number (less likely to break but still wrong).
Coerce to int(round(price)) at the top of each set_price implementation
so the boundary is enforced regardless of caller type. Also fix the
test to use integer arithmetic (v - 1 not v - 1.00).