[1/3] Support of HTTP, API Version and ClientId (#22)

* 1) Support of logging to custom domains
2) Support of HTTP insecure mode
3) Support of Client connection field
4) Bump to API version 50.0

* Fix for junit version
set version of xstream to compatible with current code

Co-authored-by: gorchenok <36301671+gorchenok@users.noreply.github.com>

Author: spuliaiev-sfdc

README.md

@@ -65,12 +65,16 @@ jdbc:ascendix:salesforce://;sessionId=uniqueIdAssociatedWithTheSession
 | _password_ | Login password is associated with the specified username. <br>**Warning!** A password provided should contain your password and secret key joined in one string.|
 | _sessionId_ | Unique ID associated with this session. |
 | _loginDomain_ | Top-level domain for a login request. <br>Default value is _login.salesforce.com_. <br>Set _test.salesforce.com_ value to use sandbox. |
+| _https_ | Switch to use HTTP protocol instead of HTTPS <br>Default value is _true_|
+| _api_ | Api version to use. <br>Default value is _50.0_. <br>Set _test.salesforce.com_ value to use sandbox. |
+| _client_ | Client Id to use. <br>Default value is empty.  |
 
 
 ## Supported features
 1. Queries support native SOQL;
 2. Nested queries are supported;
-3. Request caching support on local drive. Caching supports 2 modes: global and session. Global mode means that the cached result will be accessible for all system users for certain JVM session. Session cache mode works for each Salesforce connection session separately. Both modes cache stores request result while JVM is still running but no longer than for 1 hour. The cache mode can be enabled with a prefix of SOQL query. How to use:
+3. Request caching support on local drive. Caching supports 2 modes: global and session. Global mode means that the cached result will be accessible for all system users for certain JVM session. Session cache mode works for each Salesforce connection session separately. Both modes cache stores request result while JVM still running but no longer than for 1 hour. The cache mode can be enabled with a prefix of SOQL query. How to use:
+=======
   * Global cache mode:
   ```SQL
   CACHE GLOBAL SELECT Id, Name FROM Account