PropagateServiceTemplate for services with data tables

Updating a service template performs an asynchronous creation of project services using PropagateServiceTemplate.

This propagation works fine except for those services that also have a separate table to store some fields data like issue_tracker_data, jira_tracker_data and open_project_tracker_data at the moment, see: https://gitlab.com/gitlab-org/gitlab/-/blob/v12.10.0-rc20200415152739-ee/app/models/project_services/data_fields.rb#L45-47

We need to extend the propagation to also cover the services with separate tables.

Addendum: This will help us to implement Option A #213568 (comment 323577243).

Edited Apr 17, 2020 by Arturo Herrero