Move StringCodec from CMS to reusable Hippo Service

• Move code to a Hippo Service that lives in the repository
• Use Hippo Service instead of CMS service in the CMS
• Create Jenkins builds

The documentation page https://www.onehippo.org/library/concepts/content-repository/node-name-encoding.html describes the old configuration mechanism. It basically stayed exactly the same, except for the configuration location. The new configuration location is /hippo:configuration/hippo:modules/stringcodec/hippo:moduleconfig.

Example test scenario A:

1. Add property /hippo:configuration/hippo:modules/stringcodec/hippo:moduleconfig/encoding.node.nl with value "org.hippoecm.repository.api.StringCodecFactory$IdentEncoding"
2. Create a new document in the Content perspective. In the English content tree, the auto-generated URL name should be as before (with dashes etc.). But in a Dutch content tree the auto-generated URL should become equal to the document name because it uses "identity encoding" (i.e. change nothing) instead of URI encoding.

Example test scenario B:

1. Set property /hippo:configuration/hippo:modules/stringcodec/hippo:moduleconfig/encoding.node to "org.hippoecm.repository.api.StringCodecFactory$IdentEncoding"

1. Create a new document in the Content perspective in any content tree. The auto-generated URL name should now always be equal to the entered document name because it uses "identity encoding" by default.