osd/OSDMap: don't set weight to IN when OSD is destroyed

osd/OSDMap: don't set weight to IN when OSD is destroyed

Since commit 4e28f9e63644 ("osd/OSDMap: clear osd_info, osd_xinfo on
osd deletion"), weight is set to IN when OSD is deleted.  This changes
the result of applying an incremental for clients, not just OSDs.
Because CRUSH computations are obviously affected, pre-4e28f9e63644
servers disagree with post-4e28f9e63644 clients on object placement,
resulting in misdirected requests.

Fixes: http://tracker.ceph.com/issues/19119
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
(cherry picked from commit a6009d1039a55e2c77f431662b3d6cc5a8e8e63f)