Reason/Context

• We have support for ClientOpts struct, which will work as global client options for each command and help to initiate a new microcksClient according to the global options.
• All the current commands who are initiating a microcks client should implement it to create a microcks client based on the global configuration, and it will reduce the overhead of setting some flags for each command.

Description

Benifits

• This feature will remove flags like verbose, insecureTLS, caCerts from each command, and we can mention them in root command and make it persistent to all sub commands.
• We can also use flags like --context to perform something in specific context dynamically and --config-path to load the configs from custom config location on the fly.
• We can manipulate the configs of the MicrocksClient for specific command.

Implementation ideas

No response