Generated OData query string escaping

This fixes an issue with generated OData queries not being escaped. If any values in the query string (like string or date literals) contained URL characters then the query would be mangled by the OData library on the backend.

This change just wraps generated OData query parameters in Uri.EscapeDataString calls in the MobileServiceUrlBuilder. And corresponding Uri.UnescapeDataString calls in the parse function.