Set insecure tls on server level instead of command level

[gangefors]

Describe the solution you'd like to see
Currently there are several commands that do not support --insecure-tls option but should support it, example jf rt repo-create. The usage report also does not adhere to the insecure tls option since nothing is saved on the server level.
Since the TLS certificates are on the JFP server and not a single endpoint it would make sense to set the TLS validation on the server level instead of the individual command.
This would also make sure that all commands that talk to a server we want to ignore TLS validation on will work.

Allow a user to set a flag on each configured server that will select if calls to the server should validate certificates or not.
Let the user set this for each service URL or for all endpoints.

Example:
--insecure-tls would set it for all endpoints
--artifactory-insecure-tls would set it for --artifactory-url
--distribution-insecure-tls would set it for --distribution-url
--mission-control-insecure-tls would set it for --mission-control-url
--pipelines-insecure-tls would set it for --pipelines-url
--xray-insecure-tls would set it for --xray-url