Use wildcard char for pulsar version.

Revisions to Kubernetes coexecution pods.

- Don't hardcode the job ID - it makes Galaxy mapping tricky, seems to be not reason to anyway.
- Don't assume tool execution container has bash.
- Rev to this version of Pulsar.

Kubernetes Two-Container Pod Staging and Exec

This should just work with new Galaxy YAML job configs, embedding paths to YAML files in XML config files was awkard.

Testing for Kubernetes installed with Docker for Mac:

- Run `make build-coexecutor-container`
- Install and start rabbitmq on the localhost with Homebrew.
- PULSAR_TEST_INFRASTRUCTURE_HOST=docker.for.mac.localhost  PULSAR_TEST_FILE_SERVER_HOST=0.0.0.0 PULSAR_RABBIT_MQ_CONNECTION='amqp://guest:guest@localhost:5672//' nosetests test/integration_test.py:ExternalQueueIntegrationTests.test_integration_kubernetes

Allow configuring the "pulsar" app from command-line with base64 encoded JSON so now shared file system with Pulsar container is needed. Improve "integration" testing to ensure staging up and down occurs with pulsar-submit.

This manager is designed to just handle one job. It should be able to stage a job, write a command line to the job directory, and wait for an exit code to appear. Meant to be used alongside a container that actually runs the resulting tool.

Sync "recent" galaxy runner util changes.

Update job_conf_sample_mq.xml

Fix duplicate inputs being a problem when staging Galaxy files.

Fix a method missing problem.

Bad merge of really old branch?

Fix deprecated ``assertEquals()``

See https://docs.python.org/2/library/unittest.html#deprecated-aliases

Fix amqp_exchange_factory on python 3

fix parameter label

Minor docs updates

Added support for overriding config through environment variables