Implement "template" mechanism to create URLs for resources based on existing data

Scenarios for this story are given in https://docs.google.com/spreadsheets/d/1Yqy5gOd_6O_Ys_EpdPs5nUsBUVO1OCCPmslWQhT62f0/edit?usp=sharing - see the "CustomisedURL" column for examples of how platform URLs can be different to the original URLS supplied by the vendor/kb

Sometimes when resources are hosted on a platform, the URL for a resource required for a specific purpose can be different to the URL for the resource supplied by the vendor or knowledgebase.

These variations typically occur at platform level.

This story is to create a "template" mechanism which can be used to specify multiple templates per platform which can be used to create URLs based on existing data. The template mechanism will the same as used by the Proxy configuration (defined in https://issues.folio.org/browse/ERM-1155)

All PTIs on a platform would use the templates to create multiple URLs which could then be used in display or export of resources from agreements.

The templates should be definable at Platform level, and should be able to draw on information from:

• platform code (see https://issues.folio.org/browse/ERM-1135)
• platformTitleInstance (specifically URL - in the context of the template mechanism described in ERM-1155 this would be the 'inputUrl' for this purpose)

Each template should have a name which is used to describe the URLs created from the template.

e.g.
Platform: Beck Online
Name: State Library Berlin Reading Rooms
Template: "http://erf.sbb.spk-berlin.de/han/356251691/{{ inputUrl }}"

If we had a PTI with the pti.url = http://beck-online.beck.de/?vpath=bibdata/komm/GrossKapitalmarktR_7/cont/GrossKapitalmarktR.htm

Would lead to a new URL being added to the output for the PTI which was:
http://erf.sbb.spk-berlin.de/han/356251691/beck-online.beck.de/?vpath=bibdata/komm/GrossKapitalmarktR_7/cont/GrossKapitalmarktR.htm