march: Require all land units to start in the same sector

The capability to march land units spread over several sectors is
obscure and rarely useful.  Accidental use is probably more frequent
than intentional use.  Issues:

* Interactive prompts show only the leader's position, and give no
  clue that some land units are actually elsewhere.

* Path finding is supported only when all marching land units are in
  the same sector.

* In each step, the bmap is updated for the leader's radar.  The bmap
  is not updated around other marching land units.  Already odd when
  all units are in the leader's sector, and odder still when some are
  elsewhere.

* Interdiction becomes rather complex.  For each movement, every
  sector entered is interdicted independently.  This means the same
  ship, land unit or plane can interdict multiple times.  Interdiction
  order depends on the order the code examines land units. which the
  player can control.  This is all pretty much undocumented.

* Complicates the code and its maintenance.  Multiplies the number of
  test cases needed to cover march.

I feel we're better off without this feature.

Signed-off-by: Markus Armbruster <armbru@pond.sub.org>

info/march.t

@@ -3,7 +3,8 @@
 .LV Basic
 .SY "march <LAND UNIT/ARMY> <ROUTE|DESTINATION>"
 The march command is the \*Qmove\*U command applied to land units.
-You can control one unit or an entire army with it.
+You can control one unit or an entire army with it, but they must all
+start in the same sector.
 .s1
 Land units may only move into sectors you own, sectors of countries
 you are allied with or deity-owned sectors with 1 exception.  Spies.  Spies
@@ -115,10 +116,6 @@ For example,
 war band #18 stopped at -5,-3
 .FI
 .s1
-Note that if you are marching multiple units, you may only specify a
-destination sector on the command line if all the units start in the
-same sector.
-.s1
 See \*Qinfo Mobility\*U for the mobility cost to march land units.
 .s1
 Moving a unit through a sector that has been mined