Send client type when invoking ALM API so that it can be bypass the restriction of access after turning on API Key restriction.

The correct process is as follows:
1. customer admin add a client type into extended white list in ALM.
2. customer admin tells the users the client type name.
3. users set the client type when executes ALM Jenkins Plug-in.

 
Example source code to set client type:

ALM Productized REST scenario:
• /api/authentication/sign-in:

Add Header:
Key Value
ALM-CLIENT-TYPE %CLIENT_TYPE_NAME%

ALM Technical Preview scenario
• /qcbin/rest/site-session:

Add the following XML node to the posted data:
<session-parameters>
…
<client-type>·</client-type>
…
</session-parameters>