RPLProactor - dispatch operation handler based on expected events

Remove check of occured events against hard coded expected events.
Instead check occured events against events that the socket operation
is actually waiting for.
RPLProactor:  Implement SSL path for read/write
RCommHost:  return error code from CopyString rather than making up and error code
RPLProactor:  add API function to enable SSL for a socket
RPLProactor:  implement function to put accepted socket under SSL control
RPLProactor:  revoke the flags the operation waited for
RPLProactor:  add a user data slot to sockets
RLog - print integer values in hex
RPLProactor:  bugfix - revoke wait flags after connect

SSL sockets don't deliver an application callback after a
connection was established.  This is because the subsequent
step of performing the SSL_connect() is done.
This means that the wait flags are not automatically revoked
by the application delivery.
RCommHost:  test scripts - turn on full logging
RPLProactor:  bugfix - don't retract POLLET from wait flags
RPLProactor:  log socket and fd when creating socket
RComm - added initialization of SSL
RPLProactor:  reset event flags before adding new ones
RPLProactor:  bugfix - ssl connect wait flags for wrong socket operation

When an SSL socket needs readability or writability during
SSL_connect the read/write wait condition needs to be set
for the _connect_ operation - not the read/write operation.
RPLProactor:  bugfix - SSL context need to have private keyfile
RPLProactor: bugfix - distinguish regular/ssl case on accept
RPLProactor:  include wait flags in debug logging
RPLProactor:  wait flag change must _always_ copy new flags to current flags

The current code did not do this consistently.  If the superset of
all wait flags (across all socket operations) stayed the same the
current flag set was not recreated.  This is incorrect.
RCommLib - make the use of SSL configurable