Added multitermvectorsrequest
Added multi terms vector request/response crud.
Refactored many things to not repeat too much in MultiTermVectors infrastructure..
refactored some variable names
TermVectorFields.terms(field) didn't return null field was null
Refactored term vector test to allow usage in multi term testing
Referring to missing indexes now reported properly as an failure (was exception)
Rest actions for multi term vectors
Minor fixes to Rest actions for multi term vectors
 add locale
Added multitermvectorsrequest
Added multi terms vector request/response crud.
Refactored many things to not repeat too much in MultiTermVectors infrastructure..
refactored some variable names
TermVectorFields.terms(field) didn't return null field was null
Refactored term vector test to allow usage in multi term testing
Referring to missing indexes now reported properly as an failure (was exception)
Rest actions for multi term vectors
Minor fixes to Rest actions for multi term vectors
fix term vector api

The previous loading of term vectors from the top level reader did not use the
correct docId. The docId in Versions.DocIdAndVersion  is relative to the segment
reader in Versions.DocIdAndVersion and not to the top level reader.
Consequently the term vectors for the wrong document were returned if the
document was not on the first segment of the shard.