now client and server agree that only shares with associated writes in
`tw_vectors` are considered when computing cost

The remote method does not expose the renew_leases parameter, intentionally.

Previously an active lease on *any* share would cause us to disable lease
renewal entirely - including for newly written shares.

Now we will add a lease to any changed share that needs one, either because it
is growing or because it has no unexpired lease.

Previously this only exercised creation when no shares existed.  Now it will
create some shares and then create some more.

There is no longer an extra bool argument controlling lease renewal that we
have to protect from use by clients.

Turn off implicit lease renewal for allocate_buckets

Make better decisions about lease renewal

so don't expect to see empty lists in the tests

This means the test suite can actually exercise logic that depends on
different lease expiration times for different shares in one bucket.

now that the server actually returns different info for different shares, we
can, and we should, and we must