Add XINDEXExceptions for Increment 3 Phase 3

All exceptions were generated using the XINDEXExceptgen.py utility for
Increment 3 Phase 3.  The signed waivers can be found at the OSEHRA Jira
issue.

OSEHRA-Id: http://issues.osehra.org/browse/VAF-133
Change-Id: I5ed24c3cf647cd7ce9ad8ebdb0e2931d7af2661d
Add documentation for installing Cache.dat file

Add a rST documentation file that instructs the user on how to use a
downloaded CACHE.dat file for VistA instead of importing from the OSEHRA
Repository.  Add a line in the README file to ensure that the file is
known.

OSEHRA-Id: http://issues.osehra.org/browse/OAT-114
Change-Id: I6488ee716990ff1cc171e62fab007396cd41bf5a
Add XINDEXExceptions for VAEE Increment 3 Phase 2

All exceptions were generated using the XINDEXExceptgen.py utility for
Increment 3 Phase 2.  The signed waivers can be found at the OSEHRA Jira
issue

OSEHRA-Id: http://issues.osehra.org/browse/VAF-133
Change-Id: Ic763388a3dd12da2789d86f6e35370e502e1ee77
Add references to instructions on cloning VistA-M repo

The import and PrepareMComponents do not have any links to the
ObtainingVistAMCode.rst file. This could be confusing for a new user, who
may have missed that file.

Add links in the rST documentation for ImportCache, ImportGTM and
PrepareMComponents that point to the instructions for cloning the VistA-M
repository.

OSEHRA-Id: http://issues.osehra.org/browse/OAT-115
Change-Id: I0293ef7cd28dbecccc8d2dacee08285cf78a1742
Update ReportXINDEXErrors parsing logic

Add a '%' to the regular expressions that are used to capture the name of
the reported routine.  The parser would normally miss routines that
started with %, "%ZTLOAD" in the Kernel Package.

OSEHRA-Id: http://issues.osehra.org/browse/OAT-113
Change-Id: I065eefc7cdfd400c91276321034f5b0b9376eda5
Merge "Add XINDEXExceptions for Increment 3 Phase 3"
Merge "Add XINDEXExceptions for VAEE Increment 3 Phase 2"
Merge "Update ReportXINDEXErrors parsing logic"
Fix line endings part 2 & Fix xinetd.d scripts

If a repository is already cloned and a user does a 'git pull' to update
the repository on a windows machine the line endings for the shell
scripts will be incorrect. This change will force line endings to be
line feeds and git shouldn't complain about the change due to the
.gitattributes in a previous commit.

In a previous commit which allowed changeable instance names a couple of
files were missed. This implements a quick fix to search and replace the
hard coded default of foia to $instance.

Change-Id: If69d77db3f4c642ceec44a7cd2fa1d4119e0c006
OSEHRA-Id: http://issues.osehra.org/browse/VAF-162
OSEHRA-Id: http://issues.osehra.org/browse/VAF-163
Merge "Fix line endings part 2 & Fix xinetd.d scripts"