Add an option to `tedge connect` to prevent listener creation

[rina23q]

Is your feature improvement request related to a problem? Please describe.
When users have an already configured local MQTT broker, the listener settings created by tedge connect can conflict with the existing broker configuration.

For example, settings like mqtt.bind.address and mqtt.bind.port always have default values.

mqtt.bind.address=127.0.0.1
mqtt.bind.port=1883

Then, tedge connect always creates this mosquitto configuration file. Currently, there is no way to prevent this file's creation.

File: /etc/tedge/mosquitto-conf/tedge-mosquitto.conf

per_listener_settings true
connection_messages true
log_type error
log_type warning
log_type notice
log_type information
log_type subscribe
log_type unsubscribe
message_size_limit 268435455
listener 1883 127.0.0.1
allow_anonymous true
require_certificate false

If a user has already a configured broker, this forced common configuration file might create issues such as:

• Listener collision (same IP and port)
• Creating a new listener and opening a port with unwanted security settings
• Unwanted mosquitto log settings

Describe the solution you'd like
Introduce a new option to tedge connect that prevents the creation of the tedge-mosquitto.conf file.

Describe alternatives you've considered

Additional context
This problem was discovered while working on #3823. In that scenario, users were using already configured listener with username and password authentication on the local broker. The mosquitto configuration file created by tedge connect forces the creation of a new listener that lacks username/password authentication. This is unwanted behavior.