cephadm: wait for latest osd map after ceph-volume before OSD deploy

cephadm: wait for latest osd map after ceph-volume before OSD deploy

after ceph-volume creates an OSD, the cached osd map of the mgr can
lag behind the monitors, then get_osd_uuid_map() misses the new osd
id and deploy_osd_daemons_for_existing_osds() skips deploying the
cephadm daemon, which reports a misleading "Created no osd(s)" while
the osd exists.

This behavior is often seen with raw devices. (lvm list returns quicker).

This also fixes get_osd_uuid_map(only_up=True) as the previous branch
never populated the map when 'only_up' was true.
Now we only include osds with 'up==1' so a new OSD created (but still down)
is not treated as already present.

Fixes: https://tracker.ceph.com/issues/75965
Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
(cherry picked from commit 56123af6477a93c62df74e23b6cf3b4fdf6b19e9)