[CHEF-21374] Using debug to warn the user about the connection failure to the lice…

[ashiqueps]

…nsing server

Description

With the removal of licensing changes from the various Chef products, the knife-18 changes are allowed to continue as it is. However, when the knife is in an air-gapped environment, there shouldn't be a warning stating that the connection to services.chef.io failed.

Hence, changing the logging type to debug from warn, so that the user will have more information if they use the debug mode, and the error will not be visible in the normal scenario.

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.