fix: incorrect datatype in config (ibm-messaging#74)

- Fixes the issue of exception when setting mq.ssl.use.ibm.cipher.mappings.
- In source code, the configuration CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS
  is defined as Type.BOOLEAN but it was being used as:
  config.getString(MQSinkConfig.CONFIG_NAME_MQ_SSL_USE_IBM_CIPHER_MAPPINGS)

Signed-off-by: A S Adil Mohammad <asadilmohammad2020@gmail.com>
Signed-off-by: Joel Hanson <joelhanson025@gmail.com>

Author: A S Adil Mohammad

src/integration/java/com/ibm/eventstreams/connect/mqsink/MQSinkTaskIT.java

@@ -139,7 +139,6 @@ public void verifyMQSslUseIbmCipherMappings() {
 
         // Check if the config reflects the change
         assertEquals(System.getProperty("com.ibm.mq.cfg.useIBMCipherMappings"), "true");
-        
         // Verify the exception messages
         connectorConfigProps.put("mq.ssl.use.ibm.cipher.mappings", "Not a boolean");
         final ConfigException exc = assertThrows(ConfigException.class, () -> {