Allow child integrations to inherit the "run-as" user from an integration template Merged

The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism.

The integration template functionality allows settings from a master template to be adopted by child integrations so that they can inherit from the master settings.

However, the final "Enable" step in the integration wizard, which specifies the web hook and "Run As" user, cannot inherit from the master template.

It should be possible for all child integrations to inherit the "Run As" user from the master template.

This is especially important when configuring a master template and using a dedicated integration user account to integrate with JIRA. All of the child integrations can be created by the individual Product Owners and inherit the JIRA credentials from the template but they cannot inherit the "Run As" user.  The Run As user is an entirely separate account owned by a different team who would then need to identify all new integrations that have been setup and switch over the Run-As user separately.