crush: (optionally?) update parent weights when marking an OSD out
It's a bit unintuitive that after marking an OSD out and waiting for the cluster to quiesce, you get more data movement as soon as you remove the OSD from the map. There can be uses for it (like if you're about to put another OSD in the same space and want to keep the recovery within the failure domain), but I think it's more generally just awkward. We should consider changing that behavior.