Add insecure option to configure

[andrewmchen]

We would like to use the CLI against shards without proper SSL certificates. (For development purposes.)

[codecov-io]

Codecov Report

Merging #118 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #118      +/-   ##
==========================================
+ Coverage    78.9%   79.04%   +0.13%     
==========================================
  Files          25       25              
  Lines        1370     1379       +9     
==========================================
+ Hits         1081     1090       +9     
  Misses        289      289

Impacted Files	Coverage Δ
databricks_cli/configure/provider.py	100% <100%> (ø)	⬆️
databricks_cli/configure/config.py	96.77% <100%> (+0.1%)	⬆️
databricks_cli/configure/cli.py	92.68% <100%> (+0.37%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9090000...94336c8. Read the comment docs.

[ericwang-db]

@andrewmchen Nice! Why did you prefer to make this a config option vs a command line option that's per command invocation (like --profile). That seems to be more in line with CURL behavior, and makes the lack of trust more explicit.

[andrewmchen]

IMO, that doesn't make a lot of sense. Whether or not the host has SSL set up correctly is super coupled to the profile so it should be configured with the profile I think.

[ericwang-db]

@andrewmchen looks good! However, could we make insecure not show up in ~/.databrickscfg when it is set to None? That happens for username/password when switching the default config to token-based auth.

[ericwang-db]

@andrewmchen made a change to make ^ happen. ericwang-db@81abbee

Could you cherry-pick and let's close this PR?

[ericwang-db]

lgtm