Consistently set 2-sigma position ranges in Hitpatterns

We define the hit resolution as 1 sigma (as needed for the various
chi2 calculations), so we should cover more than 1 sigma when setting
the hitpattern position range. One might even consider 3 sigma, but
the argument is actually mostly academic since the hitpatterns are
usually binned much coarser than the hit resolution (say, 1mm
vs. 0.1mm) so that factors of 2 or 3 in the resolution only matter at
bin boundaries, and even if a neighboring bin is missed, the one
actually set frequently belongs to a valid pattern as well. Thus, 2 vs
3 sigma here most certainly is not equivalent to going from 95% to
99.8% hit detection efficiency.
Add dummy flag to Plane and read it from the database
Add support for dummy planes to Hitpattern and HitpatternLR

Pseudo-hits in dummy planes are not recorded in Hitpattern::fHits.
We don't want to use dummy hits in fits, so there is no point. Also,
there would likely be a lot of entries if a dummy plane represents
a calorimeter or hodoscope with relatively low resolution.
Ensure synchronization of track indexes for parallel arrays and NewTrackCalc
Do not pass ROOTCFLAGS to rootcint, only INCLUDES, similar to latest Podd

ROOTCFLAGS are not needed as parameters to rootcint. In fact, on newer
Mac OS X and possibly elsewhere, some of the extra paremeters cause
rootcint to fail.
Add logic for dummy planes to Projection

This is the bulk of the new logic. All planes, including dummies, are
in a new vector fAllPlanes with corresponding allowed plane pattern
fAltPlaneCombos. The index of each plane in this vector is stored in
the plane as fAltPlaneNum. fAltPlaneCombos and fAltPlaneNum are used
for TreeSearch only. Track fitting in Roads etc. continues to use
fPlaneNum and fPlaneCombos, as before. fMaxMiss always refers to
non-dummy planes; dummy planes, if defined, are always required
(otherwise they would be more or less pointless).

This is still work in progress. The Plane class decoders should behave
differently in dummy mode.
Ensure that partnered planes are either both regular or both dummy type
Properly set fAllPartnered for MWDC, even though currently unused.
Add bugchecks for invalid plane numbers in Hit, Projection and Road classes

Dummy planes have fPlaneNum == kMaxUInt (because SetPlaneNum is never
called). Hits from dummy planes must never appear in the hit set
associated with a pattern (Node_t) found by TreeSearch, and,
consequently, also not in Road building, 2D track fitting, etc.
Ensure that GEMPlane hits don't have less resolution than fResolution

It looks like this is the only modification needed to support dummy
GEM Planes. Dummy planes will typcally have a large fResolution
(calorimeter or scintillator hit), and we need the dummy hits to
reflect this.
Add dummy mode decoder to GEMPlane. Check for appropriate detmap in dummy mode.
Add a number of forgotten code changes related to dummy planes

- Projection must Decode all planes, of course
- z-positions for generating the pattern tree must come from all
  planes, of course
- The Projection width must be derived from all planes so the
  pattern tree is wide enough
- Plane initialization can skip a lot of checks for dummy planes
- Plane::Print shou;d use fAltPlaneNum, since dummy planes have no
  valid fPlaneNum
Whitespace and comment changes
More efficient calculation of projection coordinate for dummy planes
Fix buggy Pattern assignment operator
Update misc comments
Make Road building logic (BuildInfo_t) aware of dummy planes

Aside from filling fLimits in BuildInfo_t properly, this also
makes Road::IsIn(Front|Back)Range work. These fucntions is where
TreeSearch and HitSet plane numbers and the associated bitpatterns meet.
Also keep the inverse of fRotation in Tracker

This allows efficient conversion of lab coordinates to the tracker
frame: v_tracker = fInvRot * (v_lab - fOrigin);
Treat dummy hit coords as lab coords and convert using fOrigin and fInvRot
Use correct number of planes for init of fMinNdof and fChisqLimits