Atomically scale+resize in a single call

Making scale+resize in two separate calls can lead to a window in which new dedicated dynos get spun up (causing new runtime nodes to be booted) only to be immediately terminated again once the second call lands. This collapses it into a single API call. Unfortunately the collapsed API call is only in the V3 API, so we can't use the `heroku-api` gem's methods.