Update docs
Bug fixes found and partially tested during deployment to production.

Adding here for discussion, will need testing in both cases. Specifically, install and launch a workflow with variables in the template that remain blank when launching. Also launch a new Java workflow using both wait and non-wait and make sure that no new workflow run objects are created and that the existing one is updated properly.
Iterate version number and add some tests for the ini file changes
Further fix, metadata object does not return accessions, it returns IDs which have to be translated
Disable metadata write-back (needs testing)
Silly bug with the default host check
Wrote a quick test/program that can go up to a BundleManager like a user and test all the latest workflows.

Use the command:
[seqware@seqwarevm seqware-ext-testing]$ mvn clean install -DskipITs=false -P extITs
Further integration tests while I wait for the filesystem to do its thing.

About two thirds way through Perl script using Java/Maven/JUnit equivalents. Needs testing but GATK killed my VM.
Update docs and integration tests
Multi-threaded testing of the latest workflows installed to a MetaDB, completed the Java/Maven version of our Perl integration tests.

Moving the Perl tests to storage.
Refinement for IT testing
Making misleading message less vocal (it always happens with link-workflow-run-to-parent)
Fix for GATK bundle revealed error (zero is appended on all lists of parent_accessions)
Fix for GATK-revealed issue with webapp freezing and throwing NullPointers and PSQLExceptions.

Long story short, the issue was that an underlying DBAccess class was not thread safe. This would only reveal itself under load. Fixed using a low impact ThreadLocal solution. This will eventually need to be carefully looked at to see if connections, statements, and resultsets are properly closed.
Further fixes for connection pooling and GATK workflows.

Unlike commons dbcp, tomcat dbcp allows access to an unproxied connection and statement, which is pretty dangerous.
We should consider a different or newer connection pool (newer tomcat versions allow an interceptor).
Only remaining leak should be in addRelationship as of last testing.
Futher fixes applying more careful connection and ResultSet management to other parts of SeqWare.
Removing overly verbose log which repeats over and over again.
Merge branch 'hotfix/0.13.6.3'
Merge tag '0.13.6.3' into develop

0.13.6.3

Conflicts:
	pom.xml
	seqware-archetypes/seqware-archetype-decider/pom.xml
	seqware-archetypes/seqware-archetype-decider/src/main/resources/archetype-resources/pom.xml
	seqware-archetypes/seqware-archetype-java-workflow/pom.xml
	seqware-archetypes/seqware-archetype-java-workflow/src/main/resources/archetype-resources/pom.xml
	seqware-archetypes/seqware-archetype-legacy-ftl-workflow/pom.xml
	seqware-archetypes/seqware-archetype-legacy-ftl-workflow/src/main/resources/archetype-resources/pom.xml
	seqware-archetypes/seqware-archetype-module/pom.xml
	seqware-archetypes/seqware-archetype-module/src/main/resources/archetype-resources/pom.xml
	seqware-archetypes/seqware-archetype-simple-legacy-ftl-workflow/pom.xml
	seqware-archetypes/seqware-archetype-simple-legacy-ftl-workflow/src/main/resources/archetype-resources/pom.xml
	seqware-archetypes/seqware-archetype-simplified-ftl-workflow/pom.xml
	seqware-archetypes/seqware-archetype-simplified-ftl-workflow/src/main/resources/archetype-resources/pom.xml
	seqware-common/pom.xml
	seqware-distribution/pom.xml
	seqware-meta-db/pom.xml
	seqware-pipeline/pom.xml
	seqware-portal/pom.xml
	seqware-queryengine-legacy/pom.xml
	seqware-queryengine/pom.xml
	seqware-webservice-dto/pom.xml
	seqware-webservice/pom.xml