Deprecate and remove Service Templates feature
Rationale
With the introduction of instance and group based integration management, the core use case of Service Templates (managing many integrations) is best served by this new feature. Because of this, we should deprecate Service Templates and remove it from the application, driving customers to this new feature instead.
Service Templates allowed you to set a default value across project integrations, but did not support updating that value in the future. Based on many customer interviews and discussions, this caused headaches, since configurations need to get updated periodically, and those updates require a ton of busywork when each integration had to be done individually. Managing all integrations through inheritance is a significantly better approach, saving administrators/owners time and effort, and providing better consistency across all their projects.
Impact
Usage of Service Templates was recently added to usage ping (%13.4), and needs to be evaluated against adoption of Integration Management over the next few releases.
The hypothesis is that Integration Management will quickly eclipse Service Templates in usage, but we will need to validate this before deprecating.