Improve WSDL namespace generation for ESDL service

Esdl service namespace configuration includes a base string and an optional scheme string. If the scheme string is `scapps`, the base is ignored in favor of a hard-coded *seisint* specific URL to which the ESDL defined service name is appended. For all other scheme values, the namespace is a lower case concatenation of the base, service name, method name, request optionals, and client version.**

Define a new scheme (`full` suggested) that treats the base as a template for a complete namespace. The namespace will be the result of converting the base to lowercase and applying the following variable substitutions:

• `{$service}` the service name as lowercase text
• `{$method}` the method name as lowercase text
• `{$optionals}` a comma delimited list of lowercase requested optionals (e.g., "internal") surrounded by parentheses, or empty if no optionals are requested
• `{$version}` the requested client version, or default if not specified
• `{$esdl-service}` the ESDL defined service name, with case maintained
• `{$esdl-method}` the ESDL defined method name, with case maintained

The use of `service`, `method`, `optionals`, and `version` enable the default namespace to be generated. The use of `esdl-service` enables the `scapps` namespace to be generated. A user defined combination of variables enables fuller control over the generated value.