fix #K3627 - impossible placing long worm at <0,0>

When migrating, a long worm is removed from the map to take off the
tail, then its head is put back to be treated like other monsters.
If that occurred when being forced to re-migrate during failure to
arrive from a prior migration, it wouldn't have valid coordinates
and the place_monster attempt produced an impossible warning.
(Other types of monsters don't get removed and put back so didn't
trigger the problem.)

The routine to format a monster when the data is suspect mistakenly
thought it was dealing with a long worm tail because the monster
didn't match level.monsters[0][0], so the warning inaccurately
reported the problem as "placing long worm tail".

doc/fixes3-7-0.txt

@@ -937,6 +937,10 @@ the u.ustuck hierarchy is:  swallowed by ustuck, hero poly'd into sticky form
 when a vampire gains levels and grows into a vampire lord, change its cham
 	field (shapechanger base type) from vampire to vampire lord so that if
 	it revives in base form it won't revert to plain vampire
+a migrating long worm that couldn't arrive could be placed at <0,0> while
+	setting up another migration attempt to the level, triggering
+        impossible "trying to place long worm tail at <0,0> mstate:8 on level"
+	(message is confused; it should say "long worm" without tail)
 
 
 Fixes to 3.7.0-x Problems that Were Exposed Via git Repository