[Pidgin] #4594: Split PURPLE_SSL_CERTIFICATE_INVALID into several values, corresponding to PURPLE_CONNECTION_ERROR_CERT_*

[Pidgin]

#4594: Split PURPLE_SSL_CERTIFICATE_INVALID into several values, corresponding to
PURPLE_CONNECTION_ERROR_CERT_*
--------------------------+-------------------------------------------------
 Reporter:  resiak        |       Owner:  resiak
     Type:  defect        |      Status:  new   
 Priority:  minor         |   Milestone:  3.0.0 
Component:  unclassified  |     Version:  2.3.1 
 Keywords:                |     Pending:  0     
--------------------------+-------------------------------------------------
 `PurpleConnectionError` has these SSL-related values (modelled on the
 Telepathy enum):

  * `PURPLE_CONNECTION_ERROR_ENCRYPTION_ERROR`
  * `PURPLE_CONNECTION_ERROR_CERT_NOT_PROVIDED`
  * `PURPLE_CONNECTION_ERROR_CERT_UNTRUSTED`
  * `PURPLE_CONNECTION_ERROR_CERT_EXPIRED`
  * `PURPLE_CONNECTION_ERROR_CERT_NOT_ACTIVATED`
  * `PURPLE_CONNECTION_ERROR_CERT_HOSTNAME_MISMATCH`
  * `PURPLE_CONNECTION_ERROR_CERT_FINGERPRINT_MISMATCH`
  * `PURPLE_CONNECTION_ERROR_CERT_SELF_SIGNED`
  * `PURPLE_CONNECTION_ERROR_CERT_OTHER_ERROR`

 However, `PurpleSslError` only has:

  * `PURPLE_SSL_HANDSHAKE_FAILED`
  * `PURPLE_SSL_CONNECT_FAILED`
  * `PURPLE_SSL_CERTIFICATE_INVALID`

 At least the latter should be split up so that it can be mapped to the
 right `ConnectionError` rather than just to
 `PURPLE_CONNECTION_ERROR_CERT_OTHER_ERROR`.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4594>
Pidgin <http://pidgin.im>
Pidgin