schema issues

[jsnoble]

The schema used for validation has many elasticsearch client parameters, which is fine if no api_name is listed. The schema's validateJob call also calls the ensureAPIFromConfig base method and splits it off to an api and copies its configs there for the api to use. However if an api is preconfigured and attributed to an operation, that operation should no longer have connection parameters

We do check if the configs are out of sync and throw if so, however an operation will still throw if the base schema says it requires a connection parameter even though it properly lives in its api configuration. We should investigate if its possible to allow that kind of smart checking to reduce noise and duplication of configurations