Update documentation in distance_omnibus.pro
Name conflict issue resolved (gauss2 --> guass_1)

In the Markwardt library, there is a routine gauss1.pro, which creates a 1-D
Gaussian based on an x-array and [amplitude,mean,sigma], but the order of that
array is screwy.  So, I had created my own "gauss2.pro" (increment, right?) to
use the usual output of the A array from MPFITPEAK as the input.

So, it turns out there is a gauss2.pro routine in the Markwardt library to
create a 2-D Gaussian.  If the Markwardt library is _earlier_ in the IDL search
path, then that routine is chosen, causing issues.

So, a simple rename of my hacked gauss2.pro --> gauss_1.pro should make everyone
happy, no matter in what order the IDL path is specified.  The affected
routines are listed below for reference.

	modified:   dpdf/prob_hrds.pro
	modified:   dpdf/prob_knownd.pro
	modified:   dpdf/prob_parallax.pro
	modified:   subroutines/fit_sa_spectrum.pro
	modified:   subroutines/omni_vspec.pro
	modified:   subroutines/sa_gauss.pro
	modified:   subroutines/velocity_fit_spectrum.pro
	deleted:    utils/gauss1.pro
	renamed:    utils/gauss2.pro -> utils/gauss_1.pro
Merge branch 'master' into release (gauss2 --> gauss_1)

Merge the name change of gauss2.pro --> gauss_1.pro.
Add docs/ directory, and beging to write LaTeX documentation

In theory, I can write the documentation in LaTeX, and include a script that
makes the .pdf file for the user.  Dunno how well this will work, or how much
time it will take.  Probably too much of both.
Fix collision with modified cgSymbol.pro

Because I wanted extra symbols with the ease of calling cgSymbol(), I modified
said routine to do so.  But, since cgSymbol() assumes the use of cgPS_Open,
which did not come about until after I had written mydevice.pro and myps.pro
that I use exclusively for the plots.  I had added a line into my modified
version of cgSymbol.pro to define the COMMON block _$FSC_PS_START_ and CG
structure ps_struct to appease a line in cgSymbol.pro.

Well, if one defines their IDL search path placing the distance-omnibus code
at the end, the IDL-COYOTE version of cgSymbol() is used, causing pukage.

So, I placed the line defining  _$FSC_PS_START_ and ps_struct into myps.pro
and renamed my extras version of the routine as cgSymbol_extra.pro, and shifted
any repository routines that need those extra symbols to point to my routine,
and otherwise the stock cgSymbol() will be called.

	renamed:    utils/cgsymbol.pro -> utils/cgsymbol_extra.pro
	modified:   utils/myps.pro
Merge _$FSC_PS_START_ bug fix into 'release'
Increment version to 0.9.3 in README.md
Merge branch 'master' into release
Merge pull request #6 from tbowers7/release

V0.9.3 release branch