Using default Ssl configuration via -s in pub, sub and con produces NullPointerException

[gitseti]

Expected behavior

mqtt> con -s
# Error message if the broker is not configured for default ssl
# Else connect the client with default ssl

Actual behavior

In Shell:

mqtt> con -s
# empty error log
mqttClient-MQTT_5_0-7b4ecf1d-da17-4e24-8ed6-c05840ed6f92@localhost>

-> Client is connected but without using ssl

In Logs:

java.lang.NullPointerException
	at com.hivemq.cli.commands.AbstractCommonFlags.doBuildSslConfig(AbstractCommonFlags.java:132)
	at com.hivemq.cli.commands.AbstractCommonFlags.buildSslConfig(AbstractCommonFlags.java:91)
	at com.hivemq.cli.commands.shell.ShellConnectCommand.run(ShellConnectCommand.java:77)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1729)
	at picocli.CommandLine.access$900(CommandLine.java:145)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2101)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2068)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1935)
	at picocli.CommandLine.execute(CommandLine.java:1864)
	at com.hivemq.cli.commands.shell.ShellCommand.interact(ShellCommand.java:175)
	at com.hivemq.cli.commands.shell.ShellCommand.run(ShellCommand.java:123)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1729)
	at picocli.CommandLine.access$900(CommandLine.java:145)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2101)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2068)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1935)
	at picocli.CommandLine.execute(CommandLine.java:1864)
	at com.hivemq.cli.MqttCLIMain.main(MqttCLIMain.java:73)

To Reproduce

Use pub, sub or con with the -s option

Details

• Affected MQTT CLI version(s): 1.0.0
• Used JVM version: 11.0.4 (AdoptOpenJDK OpenJDK 64-Bit Server VM 11.0.4+11)