Persist property files for Jenkins/JIRA/webhook capabilities in dockerized Codenvy

The existing integrations with Jenkins, JIRA, GitHub and BitBucket Server expect a set of property files to be in the root of the Codenvy install.

With Dockerized Codenvy the container is stateless so anything stored in the container will be lost. We need to come up with a solution so that:

1. Properties files are persisted between Codenvy restarts and upgrades.
2. Property files can be placed in the /instance/config/codenvy/ directory where the codenvy.env file is already placed (this keeps things clear and simple for users).

Codenvy version: 5.0.0+ (dockerized)

OS and version: On-premises

[TylerJewell]

@bmicklea - I think the names start with CODENVY_ according to the specification. I also think we have some unintended consequences in the CLI for names not matching that for now.

BTW, in grammar terms, Integration is plural without the S. We should remove it I think.

########################################################################################
#####                                                                              #####
#####                                  INTEGRATION                                 #####
#####                                                                              #####
#
# Codenvy can integrate with third-party systems. In some cases, the third-party
# system can trigger actions within Codenvy by invoking a Factory. In other scenarios,
# Codenvy can initiate actions within third-party systems.

# Codenvy Factory Credentials
#     A third-party system may invoke an action within Codenvy by launching a Codenvy
#     Factory. Some Factories require Codenvy user credentials for the Factory to be
#     activated. 
#CODENVY_INTEGRATION_FACTORY_OWNER_USERNAME=<username>
#CODENVY_INTEGRATION_FACTORY_OWNER_PASSWORD=<password>

# Connectors
#     The association of third-party system events with the specific Factory that 
#     should be invoked by that event is an association made with a connector. 
#     There are different types of connectors that require different parameters.
#     Replace <CONNECTORID> with a unique name for each connector that you create.
#     The <CONNECTORID> can contain standard characters.
#     Example:
#         CODENVY_INTEGRATION_JIRA_NAME=prod-jira
#         CODENVY_INTEGRATION_JIRA_FACTORY_ID=r6p0l1sfnwm99k94
#CODENVY_INTEGRATION_<CONNECTORID>_NAME=<name>
#CODENVY_INTEGRATION_<CONNECTORID>_FACTORY_ID=<factory id>
#CODENVY_INTEGRATION_<CONNECTORID>_REPOSITORY_URL=<url>
#CODENVY_INTEGRATION_<CONNECTORID>_JENKINS_JOB_NAME=<job name>

# Webhooks
#     An integrations may require a webhook into the third-party system to
#     to register and capture events to automate actions.
#     Replace <WEBHOOKID> with a unique name for each connector that you create.
#     The <WEBHOOKID> can contain standard characters. You can include as many
#     Factories with each webhook as you desire.
#     Example:
#         CODENVY_GITHUB_WEBHOOK_DEVREPO_URL=github
#         CODENVY_GITHUB_WEBHOOK_DEVREPO_FACTORY1_ID=r6p0l1sfnwm99k94
#         CODENVY_GITHUB_WEBHOOK_DEVREPO_FACTORY2_ID=g8n2t3lsidu54z88
#CODENVY_GITHUB_WEBHOOK_<WEBHOOKID>_URL=<url>
#CODENVY_GITHUB_WEBHOOK_<WEBHOOKID>_FACTORY1_ID=<factory id>
#CODENVY_GITHUB_WEBHOOK_<WEBHOOKID>_FACTORY2_ID=<factory id>

[bmicklea]

@vinokurig we’ve changed the way milestones are used - now they’re only applied to PRs and issues when the PR is merged. If you’re ready though please merge PR 1641. You’ll need to add a 1-line description of the change for the Changelog (you can add it to the PR description under a heading “Changelog”) and I’ll add release note content.