Task/392 service path service path vector

### Description
A vector of service paths can now be sent via HTTP header.
The vector is parsed and stored in ConnectionInfo.
The entire vector is sent to mongoUpdateContext and mongoQueryContext, but in these two
function, instead of passing the entire vector to lower layers, only the first member of the vector is sent -
thus imitating the old way of having just ONE service path.

So, to terminate this with service path vectors, the lower layers from mongoUpdate/Query must be fixed.

Up to now, the limitation was that a service path can not inclue more than 10 "/"-based tokens. This introduces an additional limitation of no more than 10 "comman separated" service paths in the ServicePath header. Is that correct?

(It is fine to have that limitation... I'm just asking to include it as "documentation" in the issue describing the functionality).