git issue #717 - avoid putting monsters on scare \

monster and Elbereth unless there's no other choice.

Suggested by NetSysFire, don't create new monsters on top of scrolls
of scare monster.  Not mentioned in the suggestion:  unless they are
a type of monster that isn't affected by such scrolls.  This extends
it to teleport destination too.

Avoid placing a monster on a scroll of scare monster or on engraved
Elbereth if there are other locations available.  Only performed for
callers of goodpos() who explicitly request it, which at the moment
are makemon(), rloc(), and enexto().

Also, propagate 'mmflags_nht' to a bunch of places that were left
using long or unsigned for makemon() and goodpos() flags.  I didn't
attempt to be systematic about that though.

Implements #717

doc/fixes3-7-0.txt

@@ -856,6 +856,9 @@ kicking a trapped chest and getting the exploding chest result destroyed items
 it was possible to destroy a Rider corpse with an exploding chest
 when teleporting, don't consider pits/spiked pits/trap doors/holes as unsafe
 	destination locations if hero is levitating or flying
+try to avoid locations with engraved Elbereth or scare monster scroll when
+	creating new monsters or picking teleport destinations for monsters
+	who are susceptible to those
 
 
 Fixes to 3.7.0-x Problems that Were Exposed Via git Repository