[backport 7.9] Support service registration with additional interfaces

The current HippoServiceRegistration proxies the interface of named or singleton services.
The proxy is used to set the ThreadContextClassLoader on invocation of the service.
However, sometimes additional interfaces must be proxied, for example to allow access to additional methods not to be shared across web applications.

Therefore another method will be added for registration of a service with an array of interface classes, all of which will be implemented by the proxy.
The first interface class in the array will be used for service lookup.