fix: handle insecure-tls in all commands

[fsamin]

I wasn't able to run the access-token-create command with the --insecure-tls flag.
So I suggest to handle the insecure-tls in all commands. I confirm that the lower layers of the CLI handle it perfectly.

Signed-off-by: francois samin francois.samin@corp.ovh.com

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.

---

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[fsamin]

I have read the CLA Document and I hereby sign the CLA

[eyalbe4]

@fsamin,
Thanks for creating this PR.
Just adding the --insecure-tls flag to those commands will not make it work. This is because the implementation does not use it. Unlike the mvn command, which translates this flag into maven equivalent maven options, gradle or the docker commands do not.

[eyalbe4]

@fsamin,
Please let me know if you'd like to keep this PR open.

[fsamin]

Hello,
Yes, please keep this open.
I have to rebase and check all the commands that can support --insecure-tls (i.e targeting Artifactory API) and the others.