SoapStubAdapter does not handle Set-Cookie header properly

From a field report:

if [an] extension tries to generate its own cookie via:
Set-Cookie: you_are_doomed="Now"

then client library forgets vmware_soap_session cookie, and starts sending 'you_are_doomed="Now"' cookie instead (correct behavior is to start sending both of them), instantly invalidating your session:

Salient code is: SoapAdapter.py#L1213

      cookie = resp.getheader('set-cookie')
      status = resp.status

      if cookie:
         self.cookie = cookie

Where self is an instance of the class SoapStubAdapter which holds a copy of the SOAP session cookie inside itself. The correct behavior is to follow standard HTTP client session conventions and maintain whatever cookies the server sets for the session. To do otherwise invites the strange and spurious bugs at a possible later date.