Designer SQL expressions that differ between runtime client versions must be correct to the default server

Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client.

For example, 1570 details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7.

Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service.